For years in powerbuilder we could connect to any dbms via odbc, we could use a builder (like the one we now have in vfp 8.0) to run a sql statement against a remote table, then we could change the data on the client and send the updates to the server. All these can be done now in VFP - even with some limitations like the 256 char limit. The differense is that with powerbuilder no matter if the backend is SQL server or oracle or anything, Powerbuilder can handle update conflicts. How can Powerbuilder do that in contrast with vfp 8.0, where to solve the update conflict problem we have to program differently for every specific backend (either changing the update statement or via stored procedures e.t.c.) Is this a vfp cursoradapter limitation or a backend or odbc limitation ?

Thanks for any reply
Dimitris