Locking Issues

  • Thread starter Thread starter Mike
  • Start date Start date
M

Mike

I have a split Acess 2002 database being used by about 15
people. Sometimes I can go a week without having an
issue, and then sometimes the database will lock up for
just one user and it will quickly spread to all users.
Information can be entered, but when they try and leave
the record, it will freeze up for a while before saying
something along the lines of "Cannot edit/update,
database locked."

Any ideas how I can get the database to stop locking up
on my users? Each time it does this, the only way to fix
it is to have everyone close out, then once the .ldb file
is gone they can reopen and everything will work fine
until it happens again.

Any help would be greatly appreciated!


-Mike
 
Mike,

Do you have a copy of the FE on each user's local HDD, or a common copy for
all users on a network drive ?
In the latter case - which I suspect is what you are doing - the source of
the problem is the sharing of the common FE. I had a similar situation, and
it ran fine for 4-5 months before it started giving me problems... So, my
suggestion is, give each user their own copy of the FE to run.
If you want to take it a step further, have a look at Tony Toews' auto FE
updater at:

http://www.granite.ab.ca/access/autofe.htm

Do take some time to browse through the access.multiuser newsgroup, you'll
find interesting stuff pertaining to your situation in there.

HTH,
Nikos
 
Each user has thier own FE on thier local drive. Does
this change things? I'll take a look at the newsgroup
you sent me, thanks!
 
Mike,

A local FE for each user is the wise way to go... but rules out this
possibility as the source of your problem.

Another thing worth checking: in my exprerience, shared back ends thend to
blow up quite fast, so frequent compact and repair is required. Do you do
that?
If that's any help (merely as an idea), I have made a small executable in VB
6.0 (but it can also be done in Access just as well, if VB Studio is not
available) that runs as a scheduled job every night and compacts the back
end (it also makes a back up copy before compacting, just in case...). Of
course, this job requires a machine that stays running overnight, and which
has Access installed. I do that on an old, slow P2 PC, totally insufficient
for a user to work on, but perfectly capable of handling the job, as long as
it can run the required Access version; speed is not an issue overnight, yet
it manages to compact a 40+G backend in under 40 seconds.

HTH,
Nikos
 
Back
Top