no login prompt

[Guest]

I have created a database on my computer, utilized the Security Wizard and
followed the instructions exactly and things seemed to be working as
anticipated. However, suddenly, my machine will not display a login box when
I try to access the secured database nor will it allow me into the database
that I created. It will however allow the other two users access.
This morning I used the priviliges of one of the other administrators to
remove all restrictions to users and groups as outlined in the Snelling
article and I still cannot even get a login display box to appear on my
machine.
Any idea as to what is going on here?
The security applied to other users seems to be intact.
Should I try reinstalling Access on my machine, assuming there has been some
corruption in the program!
Thanks
Rocky

 

[Lynn Trapp]

Rocky,
The login prompt fires if, and only if, the Admin user of the workgroup you
are using for a given Access session has a non-blank password. If you are
joined to the default system.mdw workgroup instead of the one that you used
to secure the database, then you will not get a prompt. The Security Wizard
should have created a shortcut for you on your desktop. Use that to open
your database.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html

 

[Jeff Conrad]

Which version of Access are you using?

How are you opening the database?
Using a desktop shortcut with the correct parameters
or are you just double clicking on the file?

Do the other users get a login prompt?

--
Jeff Conrad
Access Junkie - MVP
http://home.bendbroadband.com/conradsystems/accessjunkie.html
http://www.access.qbuilt.com/html/articles.html

in message:

 

[Chris Mills]

According to Jeff Conrad and Lynn Trapp (MVP's), Access Security is utterly
pointless and they have current postings of how to crack it.

Which is not dissimilar to Microsoft posting how to crack their own
software.

Chris

 

[Guest]

In response to both Lynn's and Jeff's questions; and a couple of items that I
forgot to mention (don't you hate when people do that!)
I am using the shortcut that the Wizard created. And I am also using the
specific .mdw file created for this datatbase, not the default system.mdw.
I am now using Access 2003 and the other do get a log in prompt.

I am not exactly sure what you mean by your statement, "the Admin user of
the workgroup you are using for a given Access session has a non-blank
password". I have assigned myself an administrator position in the admins
group and thought that I would be signing in in that position. Additionally,
I have all permissions in the the admins or users groups as suggested.

Now for the things I forgot to mention: (1) after removing all restrictions
while logged in under the other admins password, I was able to log in under
my name on her machine. Then after closing the database (which is on a
server) and returning to my machine (I thought I had the problem solved) I
did not get a logon dialog box on my machine.
(2) I originally wrote the database in Access 2000 and created the security
groups in the same. Subsequently I installed Access 2003. I think I have
accessed the database since that time but am not sure.
For frame of reference, the security did work appropriately for a period of
several months.

Lynn if I missed the point of what you were saying about be the Admin user
please try to clarify for me.

Tx
Rocky

 

[Lynn Trapp]

I am not exactly sure what you mean by your statement, "the Admin user of

the workgroup you are using for a given Access session has a non-blank
password". I have assigned myself an administrator position in the admins
group and thought that I would be signing in in that position.
Additionally,
I have all permissions in the the admins or users groups as suggested.

There is a built in user named "Admin." By default, this user's password is
blank. As long as it remains blank, there will be NO prompt for a user name
and password, and you will be "silently" logged in as this user. If you are
not getting a prompt then the Admin User's password MUST be blank in the
workgroup file you are using. If other people are getting a prompt for a
password, then they must be using a different workgroup file in which the
Admin User's password is not blank.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html

 

[Guest]

Thanks to all.
You were correct, I was pointing to the correct workgroup. However, the
shortcut did point to the correct workgroup, but somehow was being
misdirected to a different, incorrect one. I finally discovered that I had
to go to the Tools menu, Security, and Workgroup Administrator to Join the
correct workgroup. Once I did that everything worked properly.

 

[TC]

It is generally not the best idea to use the workgroup administrator
program or function to join a different workgroup file. This is
because, /all/ your databases will now prompt for a username/password,
even if they are not secured.

The usual approach is to leave the workgroup administrator program or
function pointing to the standard, default workgroup file (system.mdw),
then start each secured database via a shortcut which uses the /wrkgrp
switch to select the proper workgroup file /for that run only/. Then,
people who start a non-secured database will not be asked to log-on.
The secured databases will look secured, and the un-secured ones will
look un-secured.

Google this group for the word "wrkgrp switch" for more inforation.

HTH,
TC

 

[Guest]

Well, "been there, done that" meaning the damage is already done. How can I
undo the effect of the workgroup administrator pointing the way to a
workgroup file?
Tx
Rocky

 

[TC]

Use it to re-join the standard workgroup file (system.mdw). Then create
a shortcut which uses the /wrgrp switch to slect the proper workgroup
file for that run only.

HTH,
TC