Re: Admin/owner of the db is receiving permission message

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

"Amkor Tech" <AmkorTech@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:D17F5604-1EBC-4903-81D5-482AB6AF1BC3@xxxxxxxxxxxxxxxx
Hi Joan,

I am sorry that I did not make this clear that I am talking total about
Access security on a network located database. This is something that just
started happening for this user and she tells me that nothing has changed
other than the only other admin/creator is no longer with the company.

Is it possible that the other admin was removed as a user from the mdw file? This username may have owned or had sole permission; if they were deleted then it could cause problems.

The
.mdw is in the network folder, both users are listed, I have not verified
that the one that is able to access the db is really using the .mdw, as he
does not have a local copy on his PC.

He doesn't need a local copy on his PC. You can specify the network location for the mdw file using either a mapped drive or the UNC pathname
"path to msaccess.exe" "path to mdb" /wrkgrp "path to secure mdw"

The other user does not have a problem getting to the database, where the
security window prompting for name and password appear.

How are they getting into the database? Via a desktop shortcut; direct opening in Windows Explorer??

Could it have to do with the locking file?

I don't think so, from your description. However, to make sure, get everyone out and ensure that no ldb file remains in the folder (just delete it if one exists).

You should also make sure that the mdw file on the server isn't named the same as the backend mdb.

Users need read/create permission on the folder where the mdb/mdw reside.

--
Joan Wild
Microsoft Access MVP
.

Relevant Pages

  • Auto Signon and Joining MDW Group
    ... Client-Server architecture where the data exists on a network share ... local the MDW file on the network share and Join. ... User's table, each time the user logs into the database, they are prompted to ... users enter the same default admin password combo. ...
    (microsoft.public.access.security)
  • Re: Prevent changing *.mdw file
    ... If you've applied Access security properly, it won't matter if they change ... they won't be able to use the database at all. ... > How can I prevent change of .mdw file, ...
    (microsoft.public.access.gettingstarted)
  • Re: mdw Network issue?
    ... Are they really getting a network login prompt? ... >>> Both the database, and the MDW file reside in a shared ...
    (microsoft.public.access.security)
  • Cant find MDW file problem
    ... These users, if they want to use the program in A2003, must/always log into the same app in A97 first and then log into the app in A2003. ... At first I thought it might be a "rights" issue but I discarded that thought since they can log into the app with A2003 if they first open it (using the same MDW file) in A97. ... I create the updated version from a machine with a full version of A2003 attached to their network. ...
    (comp.databases.ms-access)
  • Re: Problem with using an mdb file by several users
    ... > shared in a network by multiple users each of them having a different ... I created an mdw file in my computer describing all the ... > database that one stayed with the old database also. ... > local mdw file will be launched. ...
    (microsoft.public.access.security)