Field level locking or record level

[David]

Hello all,
I am using Access 2002, Front End and Back End. I have a second database
that appends and also updates a main table in the Back End.

Problem is the Back End database doubles if the second database updates the
Back End when users are logged in to the Front End. Just a 1/2 step away
from corruption is my guess.

Very few fields in this main table are editable by the users. The fields
that are being updated by the sedond database are not editable by the users.

I have these setting now.
In Tools-->Options, Advanced tab:
Default Open Mode - Shared
Default Record Locking - Edited Record
Open databases using record level locking - Checked


Would it be better to change it to field level locking? If so, how do I do
this?
I do have multiple users in the front end database.
OR
Is the best solution to just run the updates from the second database once
the users are out of the database?

 

[Jerry Whittle]

What do you mean by "doubles"? The database file size doubles or the time
things take doubles?

AFAIK there is only page-level or record-level locking in Access. Give me
record locking anytime. I actually doubt that record locking would increase
the size of the database file much and that page-level locking would slow
down things even more.

If the update is causing problems and not really time critical, I'd go with
your second solution. In one of my databases I have a massive import/update
scheduled for 3am when few users would be on the system.