Unwanted Prompt for User Name & Password

[DDJ]

We have an Access database (2000 format) that, on some user's PCs, opens
(when double-clicked) without a prompt for the user name and password, while
on other user's PCs, will prompt for the user's name and password. We do
NOT want the user to have to enter their user name and password.

We followed the instructions in the Access help file for removing all
security from the database but this didn't help at all. Do we need to
delete the workgroup information files on each user's PC?

Thanks in advance for any suggestions!

Dan

 

[Rick B]

Sounds like some users still have a workgroup file that contains a password
for the Admin user.

Either delete that password, or replace the workgroup file with a stripped
down one that contains no passwords and full Admin access.

Rick B



We have an Access database (2000 format) that, on some user's PCs, opens
(when double-clicked) without a prompt for the user name and password, while
on other user's PCs, will prompt for the user's name and password. We do
NOT want the user to have to enter their user name and password.

We followed the instructions in the Access help file for removing all
security from the database but this didn't help at all. Do we need to
delete the workgroup information files on each user's PC?

Thanks in advance for any suggestions!

Dan

 

[Rick B]

Here is a response from Joan Wild to a similar question yesterday. Joan
explained it well (as she always does)...

----------------------------------------------------------------------------
--------
You co-worker's computer is joined to a workgroup that has a password set
for the Admin user.

Do a search on their computer for *.mdw and make a note of the paths.

Run the workgroup administrator (Tools, security menu in 2002/2003, Start -
Run- wrkgadm.exe in prior versions) to see which one they are joined to
currently. Try joining the standard system.mdw workgroup (usually located
in the windows system folder).


--
Joan Wild
Microsoft Access MVP



We have an Access database (2000 format) that, on some user's PCs, opens
(when double-clicked) without a prompt for the user name and password, while
on other user's PCs, will prompt for the user's name and password. We do
NOT want the user to have to enter their user name and password.

We followed the instructions in the Access help file for removing all
security from the database but this didn't help at all. Do we need to
delete the workgroup information files on each user's PC?

Thanks in advance for any suggestions!

Dan

 

[DDJ]

Voila! Thanks!

Also, if I "repoint" the mdw on another user's machine (so that it will work
with my database), is there any risk that I will be messing up another
Access database on the user's machine?

Thanks again.

Dan

 

[Rick B]

Only if another database needs that MDW to operate. If so, you could create
a new shortcut for any databse file that you wish. In the shortcut, you can
specify which mdw file to use. I do that with my users because I got tired
of walking them through the workgroup administrator everytime someone got a
new laptop or had a hardrive crash.

The target looks like...

"C:\Program Files\Microsoft Office\Office\msaccess.exe"
"C:\MDB\SomeFile.mdb" /wrkgrp "\\ServerPath\Folder\FileName.mdw"



Rick B


Voila! Thanks!

Also, if I "repoint" the mdw on another user's machine (so that it will work
with my database), is there any risk that I will be messing up another
Access database on the user's machine?

Thanks again.

Dan

 

[DDJ]

Rick,

I assume that will work in VB6 code as well? Our app ships with a number of
Access databases, only one of which (the one that was causing the problems
in this thread) does NOT have a database password (because we want our users
to be able to modify design elements, etc.). So if we ship the product with
an mdw which the code points to when opening the database, do you think this
will avoid the problem?

Thanks again,

Dan

 

[Rick B]

Outside of my area of expertise.

I guess my question is, if some databases require logging in, why not just
secure this database to the same workgroup and have the users log in? Then,
user-level security would be available to you if needed.

I have about 60 users and they use my one workgroup for just about every
Access project they do. Most of them don't even know that you can get into
Access without a password.

Rick B

Rick,

I assume that will work in VB6 code as well? Our app ships with a number of
Access databases, only one of which (the one that was causing the problems
in this thread) does NOT have a database password (because we want our users
to be able to modify design elements, etc.). So if we ship the product with
an mdw which the code points to when opening the database, do you think this
will avoid the problem?

Thanks again,

Dan