ms jet db engine cannot open.. already opened exclusively

[Andrew Brill]

One of our users is having trouble loading our software when logged into the
computer as a user - it works fine if they are logged in as an
administrator.
It's a split BE/FE design and they have around 15 other users that are fine.
This is a new workstation they are trying to setup.
The error is occuring while the software tries to verify it is the same
version as the server. The code that errors is as follows:

Set dbsWorkstation = OpenDatabase("C:\Path\File.mde")

This produces the error: " The Microsoft Jet database engine cannot open the
file 'c:\Path\File.mde'. It is already opened exclusively by another user,
or you need permission to view its data.'

Note that the above file is the same file they are currently in that is
opening itself. And yes there is a reason we don't use currentdb

I've verified the user has read, create, modify permission on the files in
that folder.

This error is a new one on me and the software product is installed at
hundreds of sites. Does anyone have any idea what might be wrong?

 

[Dirk Goldgar]

message [...]

I've verified the user has read, create, modify permission on the
files in that folder.

I'm not sure that this is necessarily the cause of the specific problem
you're experiencing, but every user must have read, create, modify, *and
delete* permission on the folder containing the database file -- and
also on the folder containing the workgroup file, if you are using
user-level security, and if that folder is different.

 

[Andrew Brill]

Thanks, folder permissions is all I could think of too. I'll get them to
double check and to make sure they have delete permission in both the app
folder and the workgroup folder.

message [...]

I've verified the user has read, create, modify permission on the
files in that folder.

I'm not sure that this is necessarily the cause of the specific problem
you're experiencing, but every user must have read, create, modify, *and
delete* permission on the folder containing the database file -- and
also on the folder containing the workgroup file, if you are using
user-level security, and if that folder is different.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)