A shared database that won't share!

[Amy Martin]

Hello,
I created a database and placed it in a shared folder at
work. I want other employees to be able to update it and
view it when I have it open. When my co-worker tries to
open the forms when I have it open, we get the
message "The Microsoft Jet database engine cannon open
the file. It is already opened exclusively by another
user, or you need permission to view it's data." I have
never set up workgroup permissions, and on the advanced
tab, I have "shared" and "no locks" checked. Does anyone
know what else I need to do to enable my coworker to
update the form? The form uses multiple linking tables
for it's data - could that be affecting it?
Thanks in advance for your help!

 

[Rick B]

Does that user have full permission to the folder in which the file lives?
Users must have full permission.

Rick B

 

[Rick Brandt]

Hello,
I created a database and placed it in a shared folder at
work. I want other employees to be able to update it and
view it when I have it open. When my co-worker tries to
open the forms when I have it open, we get the
message "The Microsoft Jet database engine cannon open
the file. It is already opened exclusively by another
user, or you need permission to view it's data." I have
never set up workgroup permissions, and on the advanced
tab, I have "shared" and "no locks" checked. Does anyone
know what else I need to do to enable my coworker to
update the form? The form uses multiple linking tables
for it's data - could that be affecting it?
Thanks in advance for your help!

Do all users have full permissions to the folder where the file resides?

(they need to)

 

[Guest]

Yes she does...so that shouldn't be the problem. It's
something with the sharing because she can open it when I
don't have it open. Any other ideas? This problem is
driving me nuts!

 

[Rick B]

nomally it would be a folder permission issue. When you have it opened, the
ldb file is there. She needs to update that ldb file. In the past this
error has always been caused by the fact that the user could not modify or
delete the ldb.

What if she opens it first? Can you then open it with no problem? If so,
I'd double-check her LAN permissions.


Rick B

 

[Guest]

I just tried having her open it first (which worked fine)
but then I received the same error message when I tried
to open it. It must be something with the permissions
associated with the form, I'm guessing....but I just
don't know how to change it!

Thanks for your help!

 

[Guest]

Also, I can't have two people opening linked tables at
the same time. But opening 2 regular tables works just
fine. Thanks so much for your help - I really need to
get this fixed!

 

[Joan Wild]

Everything you are saying points to a Windows permission issue. You say you
are using linked tables. Verify that *all* users have create,modify,delete
permission on the folder where the backend is located.

You can verify this by having each user create a text file in that folder -
can they do so?

Each user should have a copy of the frontend on their computer - you
shouldn't be sharing a copy of the frontend on the server.

 

[Lionel]

I had this problem on a dbase that had previously been working.

After driving me mad it turned out that the .ldb files* hadn't disappeared after previous use. (The application had maybe closed badly). So every time i opened, instead of creating new ldb files, the same ldb files were still in place.

I simply erased the ldb files, and presto! all hunky dory again.

(*the ldb files are a temporary file created to control possible conflicts with other users storing data in the smae place. they have the same name as the dbase, and they are in the same folder but end in .ldb instead of MDB or MDE.