Ah yes... the stored proc... Dumb question here, are you return the timestamp field to the VFP cursor? I will test this scenario myself to see if I can duplicate.



>John,
>
>I am - I created a View in the View Designer and it works while my cursor doesn't! I'm currently trying to compare properties between the view and my SPT Cursor, but don't see anything so far. Could it have something to do with the fact that my cursor is from SQL Stored Proc - ie the actual select statement is not passed from VFP? I'm starting to look at the NOCPTRANS to see if that has something to do with it.
>
>Ken
>
>>Hi Ken...
>>
>>Make sure you are using the timestamp data type on SQL, not a datetime type.... I just tested this and it does work correctly...
>>
>>>Hi,
>>>
>>>I posted this originally Sat. morning, which was probably a bad idea since a lot of those weekend posts seem to get lost amid the mass of new messages most wake up to on Monday morning, so I'll try again with apologies to those who might read it twice now.
>>>
>>>I am using SPT cursors with SQL7. I have all working well - inserts, deletes, updates, identity columns etc. Now I want to use a wheretype of 4 on the cursor (key fields and timestamp) so I add a timestamp field to the SQL table, make sure it comes across in my cursor, add it to my updatefieldnames, set the wheretype to 4 and give it a go.
>>>
>>>Well - SQL Profiler confirms that the tablupdate is NOT using the timestamp field in the generated where clause - just the keyfield as if wheretype were still set to 1. So my question is this: Is there some other trick or setting, etc. that I need to employ to get this to work? I not that the timestamp field comes across in a memo field in my cursor. Is this correct?
>>>
>>>Thanks!
>>>Ken