Exclusive access message 6

[KornGeek]

I have an Access 2000 database that I have developed. It is deployed to several customers via an InstallShield installer. This installs the front-end, back-end, mdw file, and a desktop shortcut to open the front-end via the correct mdw file. Security is set up so that the database will not open at all with any other mdw file.

When the database opens, it begins by relinking to several individual database files, and then relinking the tables in the backend. I have many customers using this without any problems.

However, I have one customer who is receiving a message stating "You do not have exclusive access to the database at this time." when they open the database. The message is displayed many times in a row. I'm guessing this is somehow related to the relinking of the tables, but there is some other processing that occurs at that point.

There is nobody else using the database when they receive this message. I have had this customer install the database to a different computer, but they received the same results. I have been unable to reproduce this on my computers.

What could be causing this? Could Windows or network permissions play some part in this? I'm (fairly) sure that it has something to do with how they are set up, but I can't figure out what it is.

Thank you.

 

[kahml]

I have experienced this problem on my own workstation while working on a client's project. It has been the most exasperating two weeks imaginable. I'd modify some code, test with the Design Admin id and it would work. I'd sign on as a user and get 31 consecutive pop-ups about exclusive use. MADDENING!

Thank you very, very much for pointing out the Acrobat issue. That is definitely one for the books!

Larry Kahm
Heliotropic Systems, Inc.

 

[TisiRaptor]

Many thanks for all the tips in this thread. I started experiencing this problem this morning on a stand-alone database and couldn't work out what was going on. A Google search brought me here so I uninstalled Adobe Acrobat 7.03 professional and it sorted the problem. I re-installed Acrobat (version 7.0 only) with a custom install and the db is fine now.

I don't know why it started happening, perhaps Adobe downloaded and installed updates in the background, but I never would have thought to look at Acrobat as the cause of the problem.

Thanks again.