System.mdw problems

[David Portwood]

When I secured my database I used the default name "System.mdw" to name the
Workgroup Information File that I created. So now anytime I open any
database at all I need to provide a password. I only wanted to secure my
app, nothing else at this time. I tried renaming the file to AppName.mdw but
received the error "Unable to find 'System.mdw'".

I finally hit on removing the password from the Admin user. Ok, so now I
don't have to provide a password except for my app, which is secured under
AppName.mdw. I'm almost 100% again, except - I still have the file
System.mdw to care for. Can I move it somewhere safe or better yet, can I
delete the thing?

 

[Joan Wild]

When I secured my database I used the default name "System.mdw" to name the
Workgroup Information File that I created. So now anytime I open any
database at all I need to provide a password.

That isn't why you are prompted for a username/password. Access ships with system.mdw and security is already implemented whenever you use Access. For all databases, it uses this system.mdw file and silently logs you in as the 'Admin' user which has full privileges.

Once you set a password for the Admin user, the login is no longer silent and you get the login prompt.

When you create a new mdw file, Access makes that the default one to use for all sessions. This is why you are getting the login for all databases.

I only wanted to secure my
app, nothing else at this time. I tried renaming the file to AppName.mdw but
received the error "Unable to find 'System.mdw'".

It's a good idea to give your secure mdw a different name than system.mdw. When you want to do is
Use the workgroup administrator ( in the tools, security menu) to see what workgroup file you are joined to by default. Click on join and rejoin the system.mdw that ships with Access (you might want to do a search for *.mdw first to locate it - be sure to include system and hidden folders in your search).

Now that you've set a 'unsecure' mdw as your default, you'd setup a desktop shortcut for your secure mdb.
The target would look like
"path to msaccess.exe\msaccess.exe" "path to your db\AppName.mdb" /wrkgrp "path to your mdw\AppName.mdw"

I finally hit on removing the password from the Admin user. Ok, so now I
don't have to provide a password except for my app, which is secured under
AppName.mdw.

Well that's not really what you want, because now you don't have to login to AppName.mdb. Further more, you are now being silently logged in as 'Admin', which shouldn't have any permissions at all.

 

[David Portwood]

I'll look for the System.mdw that ships with Access. That is what I was
trying to get back to. I did search for that once before and the search
didn't pull it up - but I might not have been searching the hidden/system
files.

And thanks also for the info about creating a shortcut for my app. I'll be
needing to do that very shortly.

When I secured my database I used the default name "System.mdw" to name
the
Workgroup Information File that I created. So now anytime I open any
database at all I need to provide a password.

That isn't why you are prompted for a username/password. Access ships with
system.mdw and security is already implemented whenever you use Access. For
all databases, it uses this system.mdw file and silently logs you in as the
'Admin' user which has full privileges.

Once you set a password for the Admin user, the login is no longer silent
and you get the login prompt.

When you create a new mdw file, Access makes that the default one to use for
all sessions. This is why you are getting the login for all databases.

I only wanted to secure my
app, nothing else at this time. I tried renaming the file to AppName.mdw
but
received the error "Unable to find 'System.mdw'".

It's a good idea to give your secure mdw a different name than system.mdw.
When you want to do is
Use the workgroup administrator ( in the tools, security menu) to see what
workgroup file you are joined to by default. Click on join and rejoin the
system.mdw that ships with Access (you might want to do a search for *.mdw
first to locate it - be sure to include system and hidden folders in your
search).

Now that you've set a 'unsecure' mdw as your default, you'd setup a desktop
shortcut for your secure mdb.
The target would look like
"path to msaccess.exe\msaccess.exe" "path to your db\AppName.mdb" /wrkgrp
"path to your mdw\AppName.mdw"

I finally hit on removing the password from the Admin user. Ok, so now I
don't have to provide a password except for my app, which is secured under
AppName.mdw.

Well that's not really what you want, because now you don't have to login to
AppName.mdb. Further more, you are now being silently logged in as 'Admin',
which shouldn't have any permissions at all.