Saving the .mdw file

A

Andeva

I am using Access 03 and have just split my database and put a copy of the
front end on each user's computer, and the destop shortcut linking the .mdw
to the front end. Do I also need to save the .mdw on each user's computer?
I'm able to open each database individually, but while I was in the database
on my computer, I was unable to enter the database from any other computer.
I was getting the error "Could not use 'admin' file already in use". Is this
because I should have the .mdw saved on each computer? I believe I've done
every other step correctly based on the advice given here. Thanks!
 
A

Arvin Meyer [MVP]

The typical practice is to put the .MDW on each machine in a specific
location. Lately (by that I mean over the last few versions) the file has
been put in the C:\System32\ folder. Secure files can be given a different
name (like Secure.MDW) and put in the same place, or you can put it
somewhere else. What is important is consistency. I have worked places where
the .MDW file was on a server with the back end, and of course, if you are
using a Terminal Server, it must be on the server. Since the file must be
available to run Access, I suggest using a unique name and putting it on
each machine in the C:\System32\ directory, where future developers will
find it easily.
 
A

Andeva

Keith, do you know why I might be getting the error "Could not use 'admin'
file already in use" when I have the .mdw saved with the back end? I had no
problem with it when I put it on each user's computer.
 
K

Keith Wilby

Andeva said:
Keith, do you know why I might be getting the error "Could not use 'admin'
file already in use" when I have the .mdw saved with the back end? I had
no
problem with it when I put it on each user's computer.

I've never had that error message so I don't know. Something to check: do
all users have full create/delete permissions to the host folders for both
front and back ends?

Keith.
 
A

Andeva

Thanks so much! That simple suggestion saved me a big headache. I thought
everyone had the rights, but apparently some didn't. It's corrected now.
 
J

Joan Wild

Another reason you could get this, even with the correct permissions, is
if the mdw and the backend files have the same name - they each need to
create a ldb file and with the same name, they can't.

Joan Wild
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top