Jeff,

>The other, and perhaps more important, question is how the hell to reestablish the entire state of a cursor? Sure, you can reestablish record pointers, but what about information concerning table buffered records - OLDVAL(), CURVAL(), EVALUATE()? Should all this stuff fly out the window? Should the client retain this information via some kind of state object or array?

I'm in the middle (muddle) of wrestling with that one too, related to some master tables that get updated quite often in a web-based app. I don't want just "last entire record saved wins", since people may be changing different fields. Ideas I'm considering:

1) Query the record the user wants to edit, return it to user as XML, data object, ADO recordset, or embedded in the VALUE= clauses of HTML form INPUTs.

2) Back at the server side, before returning the above value, persist the data in some fashion, such as a single-record dbf, or XML representation stored to disk (with filename matching a session ID of some kind).

3) When saving updated data, grab the previous values and compare to determine which fields actually changed.

As you know, that's what has to be done in some fashion unless "last record saved wins" is OK in your case. I'll post ideas in a few days after I have something working -- let us know if you find the ultimate solution.