View Single Post
  #3  
Old January 14th, 2010, 07:36 PM posted to microsoft.public.access,microsoft.public.access.formscoding,microsoft.public.access.multiuser,microsoft.public.access.queries
Paul
external usenet poster
 
Posts: 126
Default trying to minimize Write Conflicts in a multi-user database

Then it sounds like it's well worth the time to make the changes.

Thanks, John.


"John Spencer" wrote in message
...
I have a similar set up, but I only have one record open on the parent form
at any time. The user selects from a combobox (or by a search that
presents them with a limited number of records). I use this information to
identify which main record they want. Then I execute a query that returns
JUST that one record to the main form.

It is very fast and works nicely and almost no conflicts ever occur.

John Spencer
Access MVP 2002-2005, 2007-2010
The Hilltop Institute
University of Maryland Baltimore County

Paul wrote:
I have a multi-user Access 2003 database and lately a number of our users
are running into the Write Conflict message gives them the choice to
either Save Record, Copy to Clipboard or Drop Changes.

The problem occurs in a tabbed form with subforms on the different pages.

I have been told by several developers that one way to minimize the
occurrence of the Write Conflict is to put the main form's controls into
a subform and remove the Record Source from the main form. You then set
Child and Master Field links in the subforms to the value returned by the
record selection combo box on the main form (stored in a text box on the
main form).

In effect, you'd only have one record open at a time from the parent
table instead of loading multiple records into the the main form at once.

Would this in fact help reduce the number of Write Conflicts? I ask
because there are a number of events in the main form the various
subforms what would have to be modified, and I'd like to confirm that it
will accomplish something before I spend the time making those changes.

Thanks in advance,

Paul