>I am using VFP 6.0 and am having an issue with the timestamp precision between my database and VFP remote view. my database has precision of 3 digits after the decimal for seconds where as VFP has only seconds. I found the below excerpt in the VFP help looking through remote views.
>
>Has anyone had experience with this and how hard is to handle timestamps this way if comparisons are needed? Is this handled different in VFP 8.0?
>
>Excerpt from VFP help
>=====================
>Using the DataType Property
>You can use the DataType property to choose a different data type than the default. For example, you might want to download a server timestamp field to Visual FoxPro, but the default data type mapping into a Visual FoxPro DateTime field would truncate any fractions of seconds stored in the server timestamp. You might use the DataType property to map the remote timestamp field into a Visual FoxPro character field to preserve the fractions of seconds.

I think there is some error in documentation. SQL server timestamp column has nothing to do with datetime. It's a 64bits database wide unique value and incremented automatically. VFP maps it to memo (binary). Yiu could compare on timestamp field IMHO.
Cetin