"Exclusive" mode doesn't work as expected

DataMiner

Registered User.
Local time
Today, 20:01
Joined
Jul 26, 2001
Messages
336
Hi,
I have a db front end in which I've set the (tools-options-advanced) default open mode to exclusive. This works fine on the PC on which I set this mode. If I try to open a 2nd copy on that PC, I don't get an error message or anything, it just takes me back to my original instance.

Still, I can open it on a 2nd PC while it's running on the original PC, and it does not complain at all. Not only that, but on the 2nd PC, the option box still shows "shared", instead of "excusive".

From this, I guess I'm drawing the conclusion that the default open mode applies to the Access application rather than the db. I can understand that, but I don't understand why I'm still able to open the db from a 2nd PC.

In the past I have used the \excl command line option. Now even that seems to give these same results. I also note that an .ldb file is being generated even when I open in exclusive mode, which was certainly not the case in the past.

Any ideas?
 
Hi,
I have a db front end in which I've set the (tools-options-advanced) default open mode to exclusive. This works fine on the PC on which I set this mode. If I try to open a 2nd copy on that PC, I don't get an error message or anything, it just takes me back to my original instance.

Still, I can open it on a 2nd PC while it's running on the original PC, and it does not complain at all. Not only that, but on the 2nd PC, the option box still shows "shared", instead of "excusive".

From this, I guess I'm drawing the conclusion that the default open mode applies to the Access application rather than the db. I can understand that, but I don't understand why I'm still able to open the db from a 2nd PC.

In the past I have used the \excl command line option. Now even that seems to give these same results. I also note that an .ldb file is being generated even when I open in exclusive mode, which was certainly not the case in the past.

Any ideas?

Some more details on the setup would help.

What version of Access are you using?

Are you switching to a newer version of Access?

Is the front end shared (store on a "server") by multiple users?

Why do you need to open the front end exclusive?
 
Oh, never mind. I forgot that you have to include the application path in the shorcut in order for the /excl to take effect.

In other words the path in the shortcut needs to be:
"C:\Program Files\Microsoft Office\Office10\MSACCESS.EXE" c:\mydb.mdb /excl

Not just c:\mydb.mdb /excl

Thanks anyway.
 

Users who are viewing this thread

Back
Top Bottom