Issue with TIME fields.

[Ruslan Zasukhin]

On 9/13/06 11:09 AM, "Ray Veenema" <rayveenema at mac.com> wrote:

> Ruslan,
> 
> In my case I am using RB 2006r3 on a Mac using the ADK version only.
> 
> I am using the datetime fied in the database and as an example I use a string
> which looks like
> 
> INSERT INTO tablename VALUES ('field1', 1, '2006-09-01 18:00:00:123')

So SQL.
 
> The datetime field in my case is a UNIQUE INDEXED field in the table.

With index. Okay I will try make it indexed also.
 
> When I am updating the record I use the cursor from a previous select
> statement as follows:
> 
> cursor.DateTimeField("entrydate").SetString("2006-09-01 18:22:00:489")
> cursor.UpdateRecord

Aha, so SetString() plays also...
 
> I hope this helps.

I will try now SetString from V4RB.
 
> Maybe there is something in Realbasic that parses this data to the Valentina
> engine that causes the problem. Could it be something writing over the memory
> space used by the parsed data?

I have check code of V4RB and V4MD also...I do not see mistakes so far.


-------------
Yes, we have found a case to catch bug, if specify in datetime value more
spaces:

    "2006-09-01     18:22:00:489"
               ^^^^^^^

This corrupt RAM, Ivan is fixing this issue right now...


-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]