If you're not receiving a prompt for a username/password, then either (a)
you're not pointing to the correct .mdw file and are using the default
system.mdw instead or (b) there is no password for the Admin user, and
you're logging in as Admin.
The /wrkgrp switch "points" your session of Access to a specific workgroup
file, which in turn allows you to open your secured database. Your shortcut
should look like this:
"Path to MSAccess.exe" "Path to your database" /wrkgrp "Path to the .mdw
file"
Note these are FULL paths ... for example "C:\Program
Files\Office\MSAccess.exe"
You can also include user and pwd switches, but those aren't going to solve
your troubles. If you do NOT have a valid user and password combo, you will
likely not gain access to this database without resorting to one of the
password crackers available on the internet.
--
Scott McDaniel
CS Computer Software
Visual Basic - Access - Sql Server - ASP
"Jeff Amiel" <je**@amiel.net> wrote in message
news:e3**************************@posting.google.c om...
no prompt for username/pw.
When I first was setting up the shortcut the mdb, I had put the wrong
path to the mdw...and I got a dialog saying that it couldn't find
XXX.mdw....once I fixed it, the dialog went away (replaced by the
'this user doesn't have permission thing)
Now, I have a 'password' that the old application used (that used this
mdb) that user would have to type in. (not sure if it was an access
dialog or a surrounding application)...but I never get prompted when
trying to open the mdb with access. Is there a command line switch to
tell access a specific user/pw to use when opening the mdb?
No matter what mdw file you use if you are not being prompted for a
UserName and Password then you are logging in as the same user "Admin". Are you
being prompted? Normally the mdw file for a secured app will have a password
applied to the "Admin" account and it is this that causes you to get a login
prompt.
Some developers use a variation on user security where they give "Admin"
whatever permissions they want their normal users to have instead of
depriving him of all rights. This allows them to distribute their application
file without having to distribute an mdw file (users just use the default
System.mdw). A different mdw file is retained for use by the developer
and that file would require a login prompt. In that case you would not only need
the developer's mdw file, but you would also need to know a legitimate
UserName and Password.
