Hi Fabio,
Sql Server timestamp data type doesn't include any date and time info. It's equivalent of rowversion datat type in SQL-92 standard. I'm not sure why do you need an index on timestamp field in the first place. It seems to me that you're using timestamp data type where you should use datetime data type (SQL-92 timestamp).
>Hi Sergey,
>
>yes VFP traslate timestamp to Memo NOCPTRANS ( raw binary data ).
>
>I would want that VFP uses also the C(??) NOCPTRANS fields.
>
>Instead these they are not supports to you,
>if it comes forced their use,
>VFP inserts the exadecimal string of remote ODBC value. Why ?
>
>An other problem is this:
>
>VFP RV or CA generates exadecimal string ODBC for fields timestamp (M NOCPTRANS)
>
>Example: ... AND ts=0x0000000001E678C9
>
>Well.
>
>Exists a VFP native function that get me the exadecimal string of raw binary data ?
>So that I can use it in SPT commands ?
>
>This is useful also for any raw data.
>
>I need write it on FLL/DLL C code?
>
>I don't uses ?exp substitution, because SPT writing is do in "no batch asyncronous mode", and 99% VFP table/cursor are random name table SYS(2015).
>
>Fabio
--sb--