>>You've just got to the point where it got complicated, see above. You now have just a way to detect that the serverside record has changed meanwhile, nothing else. The server will not tell you which fields are different. I'd like to have a db server which would, but AFAIK they don't.
>
>for that the server would need to save each record retrieved... but you could implement a history of changes
>via timestamp / record change counter from other post ;-))
>
>>To know what changed, you'd need to retrieve the current version of the record (into a separate cursor), then compare field by field with your current record etc etc, as described in that long paragraph with ouches and parentheses above. Life is tough.
>
>Nawww, general routine to compare all the fields plus option to show all or only changed fields
>with 4 columns for fieldname, transform(newval), transform(oldval()), transform(serverval())

Yup, same thinking here. Yes, lots of work, but then do it once generally, not for each posible table separately, but as a general routine. Sounds like a candidate for framework code.