Opening the Wrong .MDB (2000/sp3 or sp4)

Topic

New Reply

Using a shortcut to open a database using the associated workgroup file is there any way to wind up opening a different database than the one specified in the shortcut?
“C:Program FilesMicrosoft OfficeOfficeMSACCESS.EXE” “S:AppPathNorthwind.mdb” /wrkgrp “S:AppPathNorthwind.mdw”
Where Northwind was secured using a workgroup file placed on the same path and called Northwind.mdw?
Yes, “S:” is a network drive, but if there was a problem resolving or accessing the mapped drive shouldn’t there be an error and not just grab some default database for the particular user?

Reply | Quote

Replies

When this happens to me i get an error saying that it couldn’t find the file.

I have never had Access just open another db instead.

Reply | Quote

When this happens to me i get an error saying that it couldn’t find the file.

I have never had Access just open another db instead.

Reply | Quote

My experience is the same as John’s: I have never seen a shortcut open another database if the target database was not available.

Reply | Quote

Thanks.
That was my experience also.
The user can’t reproduce the behavior. Am assuming this is a UFO.

Reply | Quote

Thanks.
That was my experience also.
The user can’t reproduce the behavior. Am assuming this is a UFO.

Reply | Quote

My experience is the same as John’s: I have never seen a shortcut open another database if the target database was not available.

Reply | Quote

Agree with John and Hans.

Having an MDB file and a MDW file with the same name in the same folder is not a good idea. AFAIK, they will both attempt to create an LDB file, with unknown results. I suggest that you change the name of the MDW file.

Reply | Quote

Thanks.
That was my experience also.
The user can’t reproduce the behavior. Am assuming this is a UFO.
Also a good point about the possible problem with Lock files. Our standard is to require them in separate directories.

Reply | Quote

Thanks.
That was my experience also.
The user can’t reproduce the behavior. Am assuming this is a UFO.
Also a good point about the possible problem with Lock files. Our standard is to require them in separate directories.

Reply | Quote

Agree with John and Hans.

Having an MDB file and a MDW file with the same name in the same folder is not a good idea. AFAIK, they will both attempt to create an LDB file, with unknown results. I suggest that you change the name of the MDW file.

Reply | Quote