Record locking/Batch Updates

A

AlanD

I need to update 2 fields in a table, call them 'Initials' and 'Phone'

I have 2 users. One has a list of Initials. The other has a list of
Phones. They want to input the changes simultaneously. (No adds or deletes
are needed.)

There is a separate form to update each of the fields. So user 1 cannot
change the data which is accessible to user 2.

What is the best way to minimise locking problems? One thought is to give
each user a temporary copy of the table to edit and then do a batch update
to copy say all the Initials back while keeping the stored Phones.

Alternatively, given that the datasource for the Initials Form doesn't
include Phones, can the processing when a lock is detected be made to just
continue (how?)? Presumably it would use the latest version of the record
and just change the fields in the form's datasource. Are there implications
because tables are held in cache, or are all updates written immediately?
When does a lock get released?

Thanks for any suggestions, links, samples you can suggest.

Alan
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top