Ken,

>> Now - what I do notice that is very interesting, and may have something to do with it, is this: Watching SQL Server Profiler - I notice that when I tablupdate() the SPT Cursor, VFP updates through the Stored Procedure "SP_EXECUTESQL" - when I do the same thing on the view - it passes a straight "UPDATE TABLE ..." to the back-end. Why is this? Could it be the cause of the problem?

This is to far into the process to be the cause of your problem. At this point, the UPDATE has been formed and sent to the server via ODBC. Your problem has to to with the UPDATE being formed and that's the job of VFP.

Now the behavior that you're describing is interesting in that I've witnessed the same, except for being reversed. That is, when updating data through a view, VFP forms a parameterized UPDATE which the ODBC driver sends to SQL Server using sp_executesql. When a non-parameterized UPDATE (or any command actually) is submitted using SPT, the ODBC driver passes it straight through.

I'm going to guess that VFP does some detective work to determine which column is the timestamp and then adds the column to the WHERE clause it forms the UPDATE.

-Mike