>Hi Dragan,
>
>>From what I knew and what I just re-read, the datetime field in a SQL server table has the same structure as in VFP - 4 byte integer to represent the date, 4 bytes integer for the milliseconds.
>
>SQL server stored the milliseconds. VFP only stores seconds. That's the reason why you get an update conflict error when you change a datetime field from VFP and use the "modified fields and key fields" WHERE clause for the view or cursor adapter.
>
>BTW <g>, there isn't _the_ datetime format in VFP. VFP uses at least two different formats, one in DBF files and one for MEM files.

I guess that's because VFP used to store milliseconds once upon a time - in VFP 5 and maybe 6 - but displayed only seconds, so we had the same problem in bare dbfs. The format is actually the same, but the content isn't - the milliseconds get discarded when storing into a dbf, or when there's a mix of field and a memvar in an expression. Somehow I can't extract the millisecond part anymore, which I once could.