Hi All,
Using WinXP pro/Access 2000.
I have a database that's been used for about 5 months. Transferred lots of
data from a dos based program, then the users have been using it for that 5
months. About 180000 records in one of the main files (maybe 25000 new since
the dos conversion). Been having some speed issues crop up along the way
(much faster to do same reports when I first transferred the data than now,
with the new 25000 records). So, thought I'd run Compact/Repair.
Of course I did the compact/repair on a copy of the mdb. After the c/r,
while still on the same computer, the reports that had slowed down over this
time, speeded up again. Yippee! So, I saved the old file as a backup, and
made this recently c/r'd file the one to link to for all the users (4 others
plus the one where I did the c/r, so 5 total). Only problem is, nobody else
can get at the files. Everyone else's front end says the back end is
unavailable/locked by another user when they try to link into it. Even
trying to go in and just open the backend file can't be done (so,
eliminating the front end). The computer where I did the c/r is fine--has
access to all the data, no problems. Any other user is locked out. I put
the old, un compact/repair'd file back in, and all the users can link in
fine. But, it's slow again.
I've tried compacting/repairing on a different machine and I get exactly the
same results--that user can use it, but nobody else can. I've looked thru
all the files (pre and post c/r) and nothing *looks* odd with the
structures, relationships, etc, so...
Ever heard of this happening?
Does anyone know what the heck is going on and how I might approach making
things right so that compact/repair doesn't break everything?
TIA
ron