I am working on an app that uses some large tables. To keep some of the table sizes down we move some of the records after they are no longer need to a history table where they remain until eternity.

We were getting some duplicate records in the current and history because one user deleted the record when another on a different computer was editing it. When the editing computer hits save it makes another copy from what was buffered.

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