Log In

27 Dec 2006 4:43 PM

jerrodklein313

Hi,
I have posted a couple of times before, about security issues with some
users of my db. The issues (as you may recall), involve users not gaining
access to the db, and an error message keeps returning, saying that Admin is
already in use.
So I will try again. Let me ask my first question. The users that get this
message aren't even given the opportunity to log-in. Is there a way to get
this function back?

27 Dec 2006 4:53 PM

Lynn Trapp

If they are not being prompted for a username/password then they are not
connecting to the correct .mdw file. If you have a shortcut that points to
that file, then be sure they use it to open the database.

--

Lynn Trapp
Microsoft MVP (Access)
www.ltcomputerdesigns.com

Show quoteHide quote

"jerrodklein313" <jerrodklein***@discussions.microsoft.com> wrote in message
news:E20CCD13-9BAE-4368-A47E-45576F0E2594@microsoft.com...
> Hi,
> I have posted a couple of times before, about security issues with some
> users of my db. The issues (as you may recall), involve users not gaining
> access to the db, and an error message keeps returning, saying that Admin
> is
> already in use.
> So I will try again. Let me ask my first question. The users that get this
> message aren't even given the opportunity to log-in. Is there a way to get
> this function back?
>

27 Dec 2006 4:57 PM

Rick Brandt

jerrodklein313 wrote:

> Hi,
> I have posted a couple of times before, about security issues with
> some users of my db. The issues (as you may recall), involve users
> not gaining access to the db, and an error message keeps returning,
> saying that Admin is already in use.
> So I will try again. Let me ask my first question. The users that get
> this message aren't even given the opportunity to log-in. Is there a
> way to get this function back?

I have never heard of a message "Admin already in use". However; if you have
secured your file in the "normal" way then a specific workgroup file must be
used that prompts the user for a user name and password before they can get in.
If the users having problems are not being prompted to log in then that
indicates that they are not using the correct workgroup file and "not getting
in" is exactly what should be happening.

The recommended way to provide access to users of a secured app is to provide
them with a shortcut that opens Access while specifying the workgroup file to
use for the session as well as the MDB file that should be opened. Is that what
you did or do you have your users "join" your workgroup thus making the correct
workgroup file their default?

If you gave them a shortcut, then the "not getting in" problem would indicate
that they are not using the shortcut or that it has been altered and is no
longer switching them to the correct workgroup file.

If you had them join your workgroup file then "not getting in" suggests that
their default workgroup has been changed to something else.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com