>"My memory may be faulty on this, but I do not think Remote Views of SQL Server or Oracle tables returned errors when an update was issued via TABLEUPDATE() on a record that no longer existed."
>>
>>This should be easy to test and for me it is essential to know if this is a new issue with the CursorAdapter or something I have missed when using Remote Views.
>And now have tested this on my Remote Views using Oracle 9 and Client Access for DB2 ODBC drivers and I get " Update Conflict" and Tableupdate() returns .F. when I try to update deleted record.
>And when I tested the example on bottom of page 6 in the Code Magazine Article on my remote views, I was not able to produce the same results as it reported for CursorAdapters. Tableupdate() did always return false when the update was unsuccessful and true when the update was successful.
>So my conclusion is that Remote Views using Oracle 9 and Client Access for DB2 ODBC drivers handle updates correctly. It's the same conclusion I got!. CursorAdapter is nice concept, but doesn't replace the use of Remote Views (yet).
