A bit OT: handling multiple users in DB

[Klaus Major]

Hi Josh,

> One way is to put a dateTimeLastModified column in every table, and  
> make it a timestamp data type so it automatically gets updated when  
> the record does.
> Then, when you query data, make sure you get that value and save it  
> locally.
> Then, when the user goes to "Save", check the local and remote  
> timestamps.
> If <>, then warn the user, "Someone has recently updated this record."

Thanks, I was considering something like this.

> After that, what happens depend on your application, either  
> "Overwrite" or "Cancel", or perhaps "Merge data?"
> Or perhaps you show both records side by side and the user can decide?

Ah, yes, very good idea!
Will surely provide a good user experience, thanks a lot!



Regards

Klaus Major
klaus at major-k.de
http://www.major-k.de