Hi Jim

> Haphazardly recalling records deleted from another station is not the best thing in the world to do. How does your code know that the record should not be deleted? What if the session doing the edit is the one with the wrong data? Should not the user in session 1 be told that some other session ahs deleted records out from underneath them? What about scaling up to client server where the ONLY way to know is to fire the update and get the return from the server.

Good points. All this is operating from a datahandler class. The user gets to decide, after reviewing the data in a custom messagebox, either field by field or as one big message depending on the properties of that datahandler instance. Unless that is I have set properties for that instance of my datahandler class to always recall deletes silently or leave it deleted. Each datahandler handles one table and therefore there are only a handful on each form, even big forms - usually one or two in fact.

Most of my app data is lookup-type data, with simple relationships. The volume of conflicts will be very low. This approach seemed to me to fit.

Scaling, you are right.

Cheers

Dick