Identical user names, different DB

  • Thread starter Thread starter Miaplacidus
  • Start date Start date
M

Miaplacidus

I have a shortcut that reads:

"C:\Program Files\Microsoft Office\Office10
\MSACCESS.EXE" /wrkgrp "\\Org\Administrative\Office
\FrontOfficeDB.mdw" "\\Org\Administrative\Office\ECAD.mdb"

When I Click on this file I get a logon screen and I logon
as normal. But when I inspect the wrkgrp setting using the
wrkgrp administrator it indicates that I am looged on to
system.mdw. Why is this? I thought the purpose of the
shortcut was to direct you to the correct wrkgroup file.

Here is more fun. I'm logged on as Me with Password A.
I close ECAD.mdb but leave Access open. Now I open another
database: C:\MyDocs\Test.mdb and it opens right up. Now I
close test.mdb and exit Access. I go to Mydocs and click
on the icon for test.mdb and I get a logon screen. If I
Logon as Me with Password A, then I don't have privileges.

It happens that Mydocs\Test.mdb has a user named Me but
with password B. If I log on as Me with Password B it
opens right up. Having logged in as Me with password B I
can now close Test.DB navigate to ECAD.db and open it
right up.

If I change my default wrkgrp to FrontOfficeDB.mdw I can
still log on to either database as Me, provided that I
first log on to the "correct" one.

Does this mean that when my FrontOfficeDB.mdw gets
corrupted that I can still get in with some other mdw as
long as I have one with the same username?
 
Miaplacidus said:
I have a shortcut that reads:

"C:\Program Files\Microsoft Office\Office10
\MSACCESS.EXE" /wrkgrp "\\Org\Administrative\Office
\FrontOfficeDB.mdw" "\\Org\Administrative\Office\ECAD.mdb"

When I Click on this file I get a logon screen and I logon
as normal. But when I inspect the wrkgrp setting using the
wrkgrp administrator it indicates that I am looged on to
system.mdw. Why is this? I thought the purpose of the
shortcut was to direct you to the correct wrkgroup file.

Actually the workgroup administrator does not tell you the current workgroup
file in use. It tells you what your default workgroup file is. To verify
open via your shortcut and hit Ctrl-G and type
?dbengine.SystemDB
That will tell you the mdw in use.
Here is more fun. I'm logged on as Me with Password A.
I close ECAD.mdb but leave Access open. Now I open another
database: C:\MyDocs\Test.mdb and it opens right up. Now I
close test.mdb and exit Access. I go to Mydocs and click
on the icon for test.mdb and I get a logon screen. If I
Logon as Me with Password A, then I don't have privileges.

If you are getting a login dialog by opening a mdb directly in My documents,
then your system.mdw (which you are joined to by default you say) has a
password set for the Admin user. User Me with Password A is not in the
system.mdw workgroup.
It happens that Mydocs\Test.mdb has a user named Me but
with password B.

Databases do not have users, mdw files do.
If I log on as Me with Password B it
opens right up. Having logged in as Me with password B I
can now close Test.DB navigate to ECAD.db and open it
right up.

Me with password B is in the system.mdw workgroup.
If I change my default wrkgrp to FrontOfficeDB.mdw I can
still log on to either database as Me, provided that I
first log on to the "correct" one.

Huh? You are logging in using FrontOfficeDB.mdw. So there is no log into
the 'correct' mdb first.
Does this mean that when my FrontOfficeDB.mdw gets
corrupted that I can still get in with some other mdw as
long as I have one with the same username?

If both mdw files contain the same username AND it was created using the
exact same SID. Otherwise the two 'Me' users are different.
 
Joan Wild wrote:
"If both mdw files contain the same username AND it was
created using the
exact same SID. Otherwise the two 'Me' users are
different."

Not as far as I can tell. I can use either mdw to log on
to either file. The mdw were created separately with
separate PID's. Provided I first log on to the DB which
is intended to associated with that mdw, I can then open
the other DB. However, if I first try to log on using
the "wrong" mdw, then it will fail.

I can set either mdw as the default, it works both ways.
The only common item between the mdw's is the user name,
And that username has permissions in both DB's.

Me with password A is only in one mdw, and me with
password B is only in the other mdw.
 
Joan Wild wrote:
"If both mdw files contain the same username AND it was
created using the
exact same SID. Otherwise the two 'Me' users are
different."

Not as far as I can tell. I can use either mdw to log on
to either file. The mdw were created separately with
separate PID's. Provided I first log on to the DB which
is intended to associated with that mdw, I can then open
the other DB. However, if I first try to log on using
the "wrong" mdw, then it will fail.

Yes, well you are already authenticated for the Access session when you
'open the other db'.
 
Back
Top