Sorry for the confusion. I really do not know what to tell you. With the CA, you are dealing with a cursor now instead of a Remote/Local View. The design of the CA is to manage [insert, update, delete and select] data by sending SQL commands back to the server. The only way you ever get an error back from the server is when the SQL has a syntax error, a call to a stored proc fails, or, in general, an error returned by the server. SQL databases do not consider SQL commands that finds no matching records an error.

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.

As for DBAs creating store procs, that is not their job, IMO. The design and development of the SQL database is with me, the developer. If you want the number of records updated by the server, you would need 1 stored procedure per table for UPDATEs, and 1 SP per table for DELETEs. Same goes for INSERTs, but are optional if you do not require that kind of feedback.

>I'm not meaning UPDATE sintax error, I'm writing about Update Conflicts that's not the same, in the same way, Update Conflict isn't a error, ist's a update Conflict (if we call Aerror() is just a coincidence), why my PKField doesn't exist where it should be?, maybe another user delete it, so?, we have an Update Conflic, not an error.
>
>With Views you can Catch Update Conflict and VFP programmers don't care if you are using Oracle or SQLServer, if I told to my DBAs hey guys! go on and program Stored Procedures to handle my update conflicts they could ask: WHY?, We didn't do it before with you!! I'll have to say: Opppss, because now I'm using CursorAdapter??? Or are you telling me that before CursorAdapters you didn't use Remote Views only SPT+SPs and that's the way I should deal with remote data using SQL commands?
>
>Ok, let's say I have to code Stored Procedures, how many do I have to? 1, 2 50? taking care of any different situation?... That's why I told that the workaround is an "only-few-servers-Workaround" because it's not a solution to program SPs to every action or system, I didn't do it before, why should I do now?