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.