David,

Sounds like were on the same path. Your ideas are interesting. Some sort of XML implimentation will probably be the way to go - got alot of reading to do.

Quiz - What country song does has this verse:
... ladies love outlaws like babies love a bunch of stray dogs ...


>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.