mde file in network folder

[JoeA2006]

I have placed an mde file in a network folder with a linked table that is in
a mdb file in a different drive. Although I have successfully tested the app
both from a local copy and the file on the network a user is getting the
error Jet database engine cannot open the file "F:\.... it is already in use
by another user or you need permission to view its data"

I compiled this file on my machine and place it on the network. Could that
be the problem or is it something else?

 

[RBear3]

Does that driver have full access to the F drive? Access is not like other
Windows programs. They have to be able to add, change, and delete from that
folder so they can maintain the locking file that Access creates when a
database is opened or closed.

 

[JoeA2006]

Actually, those users would not have permission to F: . So am I out of luck?
It would be close to impossible to copy this table to another drive because
it is so large. Any way to just give them access through my app only?

 

[RBear3]

I believe they have to have access to the folder in which the database
lives.

 

[Klatuu]

There are a few issues here.
First, a front end database (your mde with forms, reports, queries, etc)
should not be one the network. Each user should have a copy on their own
computer. Only the back end database (tables and relationships only) should
be on a server.

All users need full permissions to the folder where the back end is located.

Linking using Drive Letter Mapping (F:\) is not a good idea. Not all users
will have F:\ mapped to the same location. You should use UPC mapping
(\\SomeServerName\SomeFolderName)

 

[David W. Fenton]

All users need full permissions to the folder where the back end
is located.

No, they only need MODIFY permissions (read, write, modify) --
DELETE is optional.

 

[Klatuu]

They do need delete. It is necessary to be able to create and delete because
of the ldb file.

 

[David W. Fenton]

They do need delete. It is necessary to be able to create and
delete because of the ldb file.

No, they do *not* need delete. The LDB file does *not* need to be
deleted. Disallowing delete on the folder prevents a user from
accidentally (or maliciously) deleting the back end, and is rather
important.

When the LDB or the MDB itself *needs* to be deleted, the relevant
operation can be done with a user logon that has DELETE permission.
I usually set up one or two admin users in an db admin group that
has delete permission, and the regular db users don't have it. I've
been doing this since 1998 and it works just fine in all the
versions of Access I've done it with (A97 to A2K3, but not A2K7).

 

[Klatuu]

Interesting information. I don't have a way to test it now. I personally
have never seen a situation where the back end was deleted purposely or
accidently, but I see your point.