MDW file in use

[Rochelle Huff]

I have an Access 97 front-end application (SQL backend) that has been
running fine for years. My 40+ users have a local copy of the front-end and
use a server copy of the mdw file. Over the years, this mdw file has grown
to 156MB! Whenever I compact and repair it to reduce the bloat, after a few
users log onto the database, subsequent users get a ".mdw file in use"
error message and can't log in. (That's one reason the mdw file is so
big; I haven't been able to compact it for production use.) Until recently,
I just let the file grow; however, now I am getting the same error message
when using the bloated mdw file. Does anyone have any ideas on how to fix
this problem? My current workaround is for everyone to use a local mdw file
which gets updated whenver the front-end is changed. This is working since
I don't let my users change their passwords. But I'm not sure this is a
good long term solution and I am a bulldog when it comes to Access problems
that I can't solve.

Help!

 

[david epsom dot com dot au]

Also, I would say that now is a good time to re-create the MDW
from scratch - even if it means having to re-secure the application.

(david)

 

[Rochelle Huff]

Joan,

Thanks for the reply. I have been able to compact it. The problem is the
error message
"mdw file in use. Access denied." after a few users have logged using the
compacted security file. All users have full rights to the folder where the
network mdw file is stored. (Nothing has changed system wide and the mdw
file was working fine for years.) It seems to work for a few users and then
prevents others from logging in. The users currently logged in run fine.
After all the users exit Access, I have to manually delete the ldb file to
clear the problem. I hate to have to recreate the security file, but I
understand the suggestion. I'll give it some thought. In the mean time,
I'll stay with the local mdw file approach unless I can discover what is
causing the "lock".

--
Rochelle B. Huff

--
Rochelle B. Huff

Do *all* users have full permissions on the folder where the mdw is? They
need this to create and delete the associated ldb file.

I'm confused as to whether you have compacted the mdw or not. You say you
have, yet you also say you haven't been able to for production use.

There is nothing wrong with giving them a local copy of the mdw.

 

[Joan Wild]

All users have full rights to the folder where the
network mdw file is stored. (Nothing has changed system wide and the mdw
file was working fine for years.) It seems to work for a few users and then
prevents others from logging in. The users currently logged in run fine.
After all the users exit Access, I have to manually delete the ldb file to
clear the problem.

If users have full rights to the folder, then the ldb would be deleted
automatically. Since it's not, then I'd double-check the permissions.

I hate to have to recreate the security file, but I
understand the suggestion. I'll give it some thought. In the mean time,
I'll stay with the local mdw file approach unless I can discover what is
causing the "lock".

I'd go with the local copy and not worry about it, since they can't change
their passwords.