Permission Error After Compact/Repair

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have created a Visual Basic program that connects to an Access database.
The program shares the data among several users over a network. It has
worked fine for several years. However, the Access file was getting really
large. I deleted a bunch of records to try to make it smaller, but it didn't
get smaller. So I ran the utility to repair/compact the database. That
successfully made the file smaller.

However, now when my co-worker tries to use the VB program, she gets the
following error: Err#305/ The Microsoft Jet database engine cannot open
K:\Base2000.mdb. It is already opened exclusively by another user, or you
need permission to view its data.

I have tried rebooting my machine, which is where Base2000.mdb is located.
I had my co-worker re-boot as well. Without me getting back into the
program, my co-worker still got the same error message. I put the old
(non-compacted) version on Base2000.mdb back in place, and my co-worker can
get to it just fine.

Any ideas? What did the compact/repair utility do to the file that made it
appear as though it is open exclusively. Is there any way to fix it or am I
stuck using the older, larger, and slower mdb file. Help!
 
Is it possible that it's something to do with the drive mapping? Does the
co-worker's PC already map something to K:\? Just a thought.....

-AA
 
I don't think this is the case. When we put the old mdb file in the same
location, the co-worker can get in just fine. Besides, she can see the mdb
file well enough to launch it, it then gives the access error. I think if it
were a mapping issue, I wouldn't think she could see the database at all.
 
I was searching for help on another issue and thought I'd respond even though
this message is a few months old; hope it helps.

It's probably a ghost lock. Look for the .ldb extension with your file name
(K:\Base2000.ldb). That's been the case for me in the past. Make sure no one
else has the database open then just delete that .ldb file.

Natalie
 
Back
Top