General discussion

Locked

MDW File in Access 97

By KEVIN.AUSTEN ·
Are you aware of any problems caused if the *****.MDB and *****.MDW Files have the same naming convension ?

Should they be named the same ?

Problem : - Intimitantley, we are getting the following message

"Could'nt use *****.MDW, File already in use"

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

MDW File in Access 97

by sgt_shultz In reply to MDW File in Access 97

hi, the faq on access workgroup security sez you can use any conventional name for the mdw file so i bet that is not your problem. bet it's a rights issue...
I searched mskb 'mdw file already in use'
got many articles here is a snip:
'all users (including administrators) must have Read/Execute permissions on the System.mdw workgroup information file. '
hope it helps good luck

Collapse -

MDW File in Access 97

by KEVIN.AUSTEN In reply to MDW File in Access 97

Happens with all user's intimitantly, even Admin ? I think it's because the .MDB & .MDW are named the same and in the same location. Somtimes access creates an .LDB for the .MDW and can't if one is already present. But need confirmation on that?

Collapse -

MDW File in Access 97

by KEVIN.AUSTEN In reply to MDW File in Access 97

I need confirmation, but think it's because the .MDB and .MDW are named the same and are in the same location? Somtimes access creates an .LDB for the .MDW, and can't if one is already open? Not sure though

Collapse -

MDW File in Access 97

by sgt_shultz In reply to MDW File in Access 97

have you checked those permissions as i suggested - or did you just reject cuz it didn't sound right to you? there is quite a lot about it on support.microsoft.com.
good luck

Collapse -

MDW File in Access 97

by KEVIN.AUSTEN In reply to MDW File in Access 97

I will check, thankyou for your time and effort, but I think the error message is a red herring. For Example user 12345 can log in fine now, but got the error 2 weeks ago. Then anyone else who logged in after that also got the message and the database does not load. This error effects everyone. Our solution at the moment is to kick everyone out. The .LDB Closes, then everyone has access again.

Back to Software Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums