By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,510 Members | 1,437 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,510 IT Pros & Developers. It's quick & easy.

I'm confused...Access Security

P: n/a
Yes, I've read the FAQ's...

I'm still confused.
I'm trying to help out a buddy to extract data from an .mdb file that
has special 'permissions' on it.

If I try to open it with the standard system.mdw file, I get the
"Current user account doesn't have permission to covert or enable this
database".

I was able to get ahold of the mdw file that the mdb requires..and I
created a shortcut that uses the /wrkgrp option.
same result.
Yes...I used the WRKGADM.EXE to 'join' the mdw file.

Question...
How does Access know what 'user' I am?
Is it using my OS login ID? (I tried creating a user ID on windows
that had same name as a 'user' in the mdw file...no dice)

I am so confused.

Any help would be appreciated.

info....Original mdb and mdw were created in access 97. I am using
Access 2000.
when I use the /wrkgrp option, I dont have any rights to add/edit
users in the security menu under tools...just view users.groups.
Nov 12 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
"Jeff Amiel" <je**@amiel.net> wrote in message
news:e3**************************@posting.google.c om...
Yes, I've read the FAQ's...

I'm still confused.
I'm trying to help out a buddy to extract data from an .mdb file that
has special 'permissions' on it.

If I try to open it with the standard system.mdw file, I get the
"Current user account doesn't have permission to covert or enable this
database".

I was able to get ahold of the mdw file that the mdb requires..and I
created a shortcut that uses the /wrkgrp option.
same result.
Yes...I used the WRKGADM.EXE to 'join' the mdw file.

Question...
How does Access know what 'user' I am?
Is it using my OS login ID? (I tried creating a user ID on windows
that had same name as a 'user' in the mdw file...no dice)


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.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

Nov 12 '05 #2

P: n/a
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.

Nov 12 '05 #3

P: n/a
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.

Nov 12 '05 #4

P: n/a
I still dont get it.
there are other users defined in the .mdw file (I can see them when I
use the security menu in access). This also tells me that this is not
the system.mdw file (as it is relatively empty...and I have switched
my shortcut to use this for testing purposes)

why would it default to the admin user when you open the database if
there are other users defined in the mdw?

One of the users defined in the mdw is actually the owner or has
rights to several of the components/objects in the database (I used a
demo version of one of those crackers that showed what user was
associated with each object)

*grumble*

thoughts?
"Scott McDaniel" <sc***@no.spam.thedatabaseplace.net> wrote in message news:<ga********************@comcast.com>...
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.

Nov 12 '05 #5

P: n/a
Unless a password has been specified for the Admin user (not to be confused
with the Admins group), opening the database will log you in as Admin with
no password. You can add the UID and PWD command line parameters to force
opening as a specific user, even if there is no password on Admin.

Larry Linson
Microsoft Access MVP
"Jeff Amiel" <je**@amiel.net> wrote in message
news:e3************************@posting.google.com ...
I still dont get it.
there are other users defined in the .mdw file (I can see them when I
use the security menu in access). This also tells me that this is not
the system.mdw file (as it is relatively empty...and I have switched
my shortcut to use this for testing purposes)

why would it default to the admin user when you open the database if
there are other users defined in the mdw?

One of the users defined in the mdw is actually the owner or has
rights to several of the components/objects in the database (I used a
demo version of one of those crackers that showed what user was
associated with each object)

*grumble*

thoughts?
"Scott McDaniel" <sc***@no.spam.thedatabaseplace.net> wrote in message

news:<ga********************@comcast.com>...
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.

Nov 12 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.