Rich,

You could do a comparison between CURVAL() and the first user's view field contents to determine if a change was made and advise the user of it when they hit the Edit button. This is one of the stronger arguments for having an edit button.


>In a multi-user scenario a user opens a form on one workstation which uses a Local View. All records are populated into the view from the Base Table. Now another user opens the same form on another workstation and edits a record and then saves the record. Now the first user wants to edit the same record that is in his Local View and attempts to save it with the same field being edited. The first user gets an Update Violation Error and cannot save the record.
>
>Questions and Ideas:
>1. When is the best time to refresh or requery the first user’s Local View?
>2. How would you maintain keeping the form on the same record if using a view and you issued a REQUERY()? I think it would become a speed issue if the whole table was REQUERY()ed again just before the Edit command was issued.
>
>3. Keeping the current Local View as is, would requerying the current record into another view and then populating the current Local View record be a good solution?
>
>I would hate to see the user begin editing the record and then get the error after editing a lot of data. I am trying to come up with the least obnoxious scenario for the user.
>
>I have seen this discussed in several threads but I haven't seen or haven't found any great solutions. Thanks for any help you may have.