Del,

Here's another option to consider, and something I put into a c/s app. When a user retrieves a record for editing the query also retrieves the time stamp off the record at the same time. The user edits away which can be moments or hours. When they finally save the information the first thing the program does is retrieve the time stamp once again, the program then compares it to the stamp when they first retrieved the record. If the times exactly match the save finishes without issue, and updates the record stamp with the new date/time. If the times are different the app tells them that someone else made changes to the record, and tells them that if they continue they will overwrite the other users changes, or they can revert back and start again thus requerying the data if they wish.

Just one idea...

John



>Hi all:
>
>I'm deploying my first C/S application and I'm fielding the first wave of questions from the users. They are naturally accustomed to the standard desktop style applications and are getting used to the look and feel of a c/s application.
>
>Basically, their chief concern is probably typical - that of when multiple users are working on the same record, they are not seeing the changes done by the other users. I told them they needed to re-select records on the "Selection Criteria" page (basically requerying the back end). I'm thinking about adding an automatic requery on a save so they don't have to do this as often. I don't recall seeing this as a standard tactic in all the reading I've done on C/S programming. Any thoughts pro/con on doing this?
>
>Del