1 user gets when "admin" in use - but no login/password prompt

[TxBlueEyes]

I have a user that when we click on the shortcut to the secured database they
get don't get the login / password prompt box... Instead a message saying
Cannot login when "Admin" in use... when you click "OK" reverts to ACCESS...
However, all the other users of this database do not have this issue... The
Login and Password works fine, I have tested on several PC's using the
shortcut.... I am thinking it's got to be with the ACCESS Application itself
or something... Because no other users seem to have this issue... Any
suggestions?

 

[bhicks11 via AccessMonster.com]

Look at the shortcut properties - is something different about his?

Bonnie
http://www.dataplus-svc.com

 

[TxBlueEyes]

Hi Bonnie - I didn't see anything different... can you give me a hint what
exactly I might be looking for... the start in, and target are correct....
they are the same as everyone else's who are not having an issue.... I'm
stumped.... I have 2 users all together with this problem, and 18 having no
problems at all....

 

[terushb]

Hi Bonnie - I didn't see anything different - the start in and target links
are correct.... I have 18 users all working fine, and only 2 users with this
issue... You try to open up the Database and they get the In Use "Admin"
error... it's like they are login somewhere as an Admin... but they aren't...
how wierd... thank terushb

Look at the shortcut properties - is something different about his?

Bonnie
http://www.dataplus-svc.com

I have a user that when we click on the shortcut to the secured database they
get don't get the login / password prompt box... Instead a message saying

[quoted text clipped - 4 lines]

or something... Because no other users seem to have this issue... Any
suggestions?

 

[bhicks11 via AccessMonster.com]

Check your user's rights on the server/directory - read/write/delete. Are
they all working off the same server with the same rights? Is your
application split with front end/back end? What version of Access, what
network operating system, what desktop operating systems?

Bonnie
http://www.dataplus-svc.com

Hi Bonnie - I didn't see anything different - the start in and target links
are correct.... I have 18 users all working fine, and only 2 users with this
issue... You try to open up the Database and they get the In Use "Admin"
error... it's like they are login somewhere as an Admin... but they aren't...
how wierd... thank terushb

Look at the shortcut properties - is something different about his?

[quoted text clipped - 6 lines]

 

[terushb via AccessMonster.com]

Hi Bonnie,

Good point... I hadn't thought of checking their user rights, I don't believe
they were added to the server/directory/file rights, I just added them to the
ACCESS Secure Database with permissions... I will check that on monday with
My Server Administrator... Nope, this isn't a split database... I am looking
into maybe doing this, however I am a little aprehensive, because I have
heard there are sometime issues when trying to split an already secured mdb
file... I have over 18 users with the shortcut already on their database, and
are all able to get in with no problem, however what do you recommend? I am
always open to new and better possiblities... This will be a database used
daily by the users 7 days a week.... and I will be running reports on a daily,
weekly, and monthly basis... thanks for your help, U R awesome.... Tbooker

Check your user's rights on the server/directory - read/write/delete. Are
they all working off the same server with the same rights? Is your
application split with front end/back end? What version of Access, what
network operating system, what desktop operating systems?

Bonnie
http://www.dataplus-svc.com

Hi Bonnie - I didn't see anything different - the start in and target links
are correct.... I have 18 users all working fine, and only 2 users with this

[quoted text clipped - 7 lines]

 

[bhicks11 via AccessMonster.com]

Hi TBooker,

Do it when everyone's off. Keep a good backup copy of it before you split it
so you can go back if you run into problems. Go to Tools - Database
Utilities - Database Splitter and it will seperate it into a front end/back
end for you. All your tables will be linked to the back end when you are
done and you will have a seperate database with the same name except that
there is the "-be" added to the name. Play with it and check for problems -
I don't think you will have any. The only thing I do differently is: I
don't include the switchboard (if your using one) table and any lookup tables
in the back end - I keep them in the front end. That way if I change
anything in the switchboard it carries with my frontend. Just my preference.
I especially enjoy the fe/be setup because I often make changes to the front-
end that I post to the server, I have the users hit an icon on their desktops
to copy the newer version down to their desktops with my changes. With the
fe/be you have freedom of doing this without worrying about overwriting your
data. Makes it easier on the developer. The good news is you can always go
back to your backed up version if you have a problem.

If you have any problems with the tables linking, go to Tools - Database
Utilities - Linked Table Manager and relink the tables.

Bonnie
http://www.dataplus-svc.com

Hi Bonnie,

Good point... I hadn't thought of checking their user rights, I don't believe
they were added to the server/directory/file rights, I just added them to the
ACCESS Secure Database with permissions... I will check that on monday with
My Server Administrator... Nope, this isn't a split database... I am looking
into maybe doing this, however I am a little aprehensive, because I have
heard there are sometime issues when trying to split an already secured mdb
file... I have over 18 users with the shortcut already on their database, and
are all able to get in with no problem, however what do you recommend? I am
always open to new and better possiblities... This will be a database used
daily by the users 7 days a week.... and I will be running reports on a daily,
weekly, and monthly basis... thanks for your help, U R awesome.... Tbooker

Check your user's rights on the server/directory - read/write/delete. Are
they all working off the same server with the same rights? Is your

[quoted text clipped - 9 lines]

 

[terushb via AccessMonster.com]

Hey there Bonnie... Quick question on the splitting... I have already a copy
of the secured database... so that's one good thing... Okay, here I go... I
had heard that the Database Splitter will create the BE file but then will
remove change the FE to an unsecured DB, and the logon prompt will no longer
come up...So, would it be better for me to make another copy the database,
and call the database the BE. Then from the FE remove the tables (except
switchboard). From the BE I would have created from a copy remove everything
but the tables, and do a link tables... Also does the BE need to setup with
the same workgroup as the FE? I wasn't sure about that... Thanks again Bonnie.
.. I have a feeling you must be a ACCESS Guru.... Have a super day....
Tbooker

Hi TBooker,

Do it when everyone's off. Keep a good backup copy of it before you split it
so you can go back if you run into problems. Go to Tools - Database
Utilities - Database Splitter and it will seperate it into a front end/back
end for you. All your tables will be linked to the back end when you are
done and you will have a seperate database with the same name except that
there is the "-be" added to the name. Play with it and check for problems -
I don't think you will have any. The only thing I do differently is: I
don't include the switchboard (if your using one) table and any lookup tables
in the back end - I keep them in the front end. That way if I change
anything in the switchboard it carries with my frontend. Just my preference.
I especially enjoy the fe/be setup because I often make changes to the front-
end that I post to the server, I have the users hit an icon on their desktops
to copy the newer version down to their desktops with my changes. With the
fe/be you have freedom of doing this without worrying about overwriting your
data. Makes it easier on the developer. The good news is you can always go
back to your backed up version if you have a problem.

If you have any problems with the tables linking, go to Tools - Database
Utilities - Linked Table Manager and relink the tables.

Bonnie
http://www.dataplus-svc.com

Hi Bonnie,

[quoted text clipped - 15 lines]

 

[bhicks11 via AccessMonster.com]

Sorry I gave you that idea TBooker - I'm just a self taught hacker.

Here's a link to a discussion and breakdown of the steps in regard to FE/BE
security:

http://en.allexperts.com/q/Using-MS-Access-1440/Security-split-database.htm

Bonnie
http://www.dataplus-svc.com

Hey there Bonnie... Quick question on the splitting... I have already a copy
of the secured database... so that's one good thing... Okay, here I go... I
had heard that the Database Splitter will create the BE file but then will
remove change the FE to an unsecured DB, and the logon prompt will no longer
come up...So, would it be better for me to make another copy the database,
and call the database the BE. Then from the FE remove the tables (except
switchboard). From the BE I would have created from a copy remove everything
but the tables, and do a link tables... Also does the BE need to setup with
the same workgroup as the FE? I wasn't sure about that... Thanks again Bonnie.
.. I have a feeling you must be a ACCESS Guru.... Have a super day....
Tbooker

Hi TBooker,

[quoted text clipped - 26 lines]