I'm interested in solving this problem too, because I used the same data handling methodics.
In addition to described I know that Refresh() function call causes record to be deleted when record disappear from server. You may try Refresh() before any checking for changes. When changes detected, just save them. When record deleted, refresh() should delete local record too, so it will be out of scope and never saved. IMHO Refresh() after Tablerevert() will solve this too. You will need unique key for refresh() however, otherwise it will work very slowly.
Than, when you use GetFldState(-1) function, the first character shows changes in deleted flag. When it changed - record really deleted. When not - record marked as deleted because refresh() cannot find record on server.
Hope this will work.

>I am trying to work around this problem. In my save routine I look
>in the history table and see if the record is in there and apply my
>changes to that record which is ok in the grand scheme of the way the
>software operates. Because I don't want my class code to update anything
>in the current table I issue a tablerevert() on it but the only flag that
>is cleared is my deleted flag which I didn't delete to start with, the
>other user did. I still have several modified fields showing.
>
>My check for edit routine looks at check field state and sees some fields are dirty so it still wants to save it. Table revert will not clear these flags.
>
>Any ideas?
>
>Thanks...
>Thomas Martin