MDE file error 3045 - PLEASE HELP!

[Willow]

Hi

I hope you can help me with this it is driving me nuts.
I've created a database which I needed to give multiple people access
to but didn't want them messing so I created an MDE file. I ensured
that the MDB file was set to shared, not compacting and set to run
users not owners permissions before I converted.
However, if one of the users goes into the database, it does not create

and LDB file and if anyone else tries to get it, the error message:
Could not use <name>; file already in use. (Error 3045)
appears. Some of the tables in the MDE files were linking to and MDB
file, however, I have removed the links and it is still happening.
All of the help sites and articles refer to what to do if you get this
message when using a b/e - f/e MDB but I can't find anything about
getting this error with an MDE. Its the fact that the LDB file is not
being created that is really confusing.
Please help!!!!!
Willow

[deluxeinformation]

Willow wrote:

Hi

I hope you can help me with this it is driving me nuts.
I've created a database which I needed to give multiple people access
to but didn't want them messing so I created an MDE file. I ensured
that the MDB file was set to shared, not compacting and set to run
users not owners permissions before I converted.
However, if one of the users goes into the database, it does not create

and LDB file and if anyone else tries to get it, the error message:
Could not use <name>; file already in use. (Error 3045)
appears. Some of the tables in the MDE files were linking to and MDB
file, however, I have removed the links and it is still happening.
All of the help sites and articles refer to what to do if you get this
message when using a b/e - f/e MDB but I can't find anything about
getting this error with an MDE. Its the fact that the LDB file is not
being created that is really confusing.

It shouldn't matter that the file is an MDE as opposed to an MDB, so
any advice you read concerning MDB's should apply to MDE's in this
regard. Both should create lock files. Did you put a single copy of
the MDE file on a network server for everyone to use? If so, you will
need to set permissions on the folder where you put it so that each
user can both create and delete files there. In general creating a
single MDB or MDE for shared use is a bad idea and you should consider
splitting it out so that each user has a copy of the front end linking
to a single back end. If you have already done this each user will
still need permission to create and delete files in the folder on the
network where the back end is stored and on the folder on the user's
machine where the front end is stored. This is because the first user
to access a closed database must be able to create the lock file and
the last user to leave it must be able to delete it.

Bruce