Allow or deny multiple instances of a db from a shortcut

[Bill]

My machine will not start multiple instances of a front end database
using just the db name. If I attempt to start the second instance from
a shortcut that uses only the path to the db, or by double-clicking it
in Windows Explorer, it does not start a second instance, it activates
the first instance. If I first start Access, then open the db, it
starts a second instance. If I create the shortcut with the full path
to Access and then the full path to the db it will also open the second
instance.

Opening the same db on other machines will open a second instance under
all circumstances. It seems that the problem is probably a setting in
access but I cannot find it. I have tried this with a blank database
with the same results, so it is not anything like a recordset left
open.

I am using Access 2002 and Windows XP. In the Access options I have set
the default open mode to Shared but Exclusive does not change the
behavior.

I found this behavior by trying to prevent a second instance, which I
was able to do using Graham Mandeno's solution. The reason for this
question is to find if there is another way to prevent multiple
instances on machines using the run-time version of Access.

Thanks.

BillF

 

[Larry Daugherty]

It sounds like it's behaving as advertized. It's just not as you
expected.

HTH

 

[Albert D. Kallal]

Opening the same db on other machines will open a second instance under

all circumstances. It seems that the problem is probably a setting in
access but I cannot find it. I have tried this with a blank database
with the same results, so it is not anything like a recordset left
open.

Are you sure of the above?? The above does not seem right??

The way I *thought* it works is:

If you make a shortcut to the mdb (or mde) file, then it should activate the
existing copy if you click on either the mdb file, or that shortcut.

If your shortcut points to msaccess.exe, then you are in effect launching
ms-access, and THEN as a parameter supplying the mdb (or mde) file name.
(this would be the same as if you launch ms-access again, and open he file).
In this case, you get another copy running.

So, if your shortcut points to ms-access.exe, then you will get multiple
copies. If you point to, or click on the actual file then you should only
get one copy running....

I open to be being corrected on the above, but I would check that shortcut
again.....

 

[Bill]

It sounds like it's behaving as advertized. It's just not as you
expected.

HTH

BillF

 

[Bill]

Are you sure of the above?? The above does not seem right??

The way I *thought* it works is:

If you make a shortcut to the mdb (or mde) file, then it should activate the
existing copy if you click on either the mdb file, or that shortcut.

If your shortcut points to msaccess.exe, then you are in effect launching
ms-access, and THEN as a parameter supplying the mdb (or mde) file name.
(this would be the same as if you launch ms-access again, and open he file).
In this case, you get another copy running.

So, if your shortcut points to ms-access.exe, then you will get multiple
copies. If you point to, or click on the actual file then you should only
get one copy running....

I open to be being corrected on the above, but I would check that shortcut
again.....

You are correct. After checking I found the other machines that I was
using to compare this behavior do not have the full version of Access
loaded, they are using the run-time only. This seems to be a difference
between the two versions. Using the run-time will always open a new
instance of the database. This will happen using either a shortcut
directly to the db or clicking on the db in Windows Explorer.

Thank you for your help.

BillF