wrkgrp doesn't read user identified

[Lhuffst]

I have an application that has the frontend & backend on a server with shortcuts on the individual user's pc's. Currently there are 20 people whose shortcuts work fine. However, I have one that continually bypasses the shortcut info and logs in as admin.

The sortcut string I'm using is:
"\\cobwin02\SrvApRec\HCSOLDatabase\House connect 2003.mdb /wrkgrp "\\cobwin02\SrvApRec\server.mdw"


On everyone one's machine (except this one) the logon box pops up with the user name in the box. They only have to add their passwords.

On this machine, it prefills the user name box as admin.
Not sure what to look for to rectify this situation.
Thanks in advance for any help
Lhuffst

 

[JoeAtWork]

Sounds like it works just fine to me. It usually shows the name of the last successful login, so just have the person log in as themselves instead of Admin. The next time it opens, it will probably have their login name pre-filled.

 

[RGarcia87]

Also, set a password to the Admin account.

 

[lameid]

RGarcia87,

It defaults to admin which means it does not log in automatically. This means that there is a password set.

 

[Lhuffst]

Thanks everyone.I'm not sure what the problem was but I ended up creating a new shortcut with the same exact information and this time when the logon box came up, I was able to change it to another person and enter the program correctly. This was good information though. I did not know that if it defaults to admin that a password had been set. Thanks again. lhuffst

 

[lameid]

To clarify, it does not automatically log in when admin is specified if the password is set (not blank). Because you see the logon prompt and it says admin, the password must be set.

I really don't use the authentication in Access, so I am not familiar with the nuiances of it.

I create a workgroup for each group plus an administrative workgroup containing all groups. I use network security to limit permissions to workgroups and add the appropriate Group to the workgroup for people who have permission. Admin is then made a member of that group in the appropriate workgroup. Finally, I use shortcuts on the end user machines to use the wrkgrp command line switch to open the appropriate workgroup. The key to all this working is using the the same PID that was used in the administrative workgroup to create the appropriate group.