Wrkgrp Info File

[Guest]

I was 'practicing' securing my database (after backing it up) and each time I
tried it to see if it would fly, I used the same Name, organization and WID
for my newly created mdw file. I found (after a bit of head scratching) that
this doesn't work and I was merely recreating the same workgroup (so THAT'S
why they say to write it down). Does anyone know where this info is stored?

 

[Joan Wild]

I was 'practicing' securing my database (after backing it up) and
each time I tried it to see if it would fly, I used the same Name,
organization and WID for my newly created mdw file. I found (after a
bit of head scratching) that this doesn't work and I was merely
recreating the same workgroup (so THAT'S why they say to write it
down). Does anyone know where this info is stored?

It's stored in the created mdw file.

 

[Guest]

Yes, but if I delete that mdw file and start over from scratch with a new
mdw, but use the same Name, organization and WID that I used to create the
first one, I see the same custom user name that I created in the previous mdw
file whilst logging on. All before I've even created any custom users in the
new file. Doesn't that mean that the info is stored elsewhere?

 

[Joan Wild]

Yes, but if I delete that mdw file and start over from scratch with a
new mdw, but use the same Name, organization and WID that I used to
create the first one, I see the same custom user name that I created
in the previous mdw file whilst logging on. All before I've even
created any custom users in the new file. Doesn't that mean that the
info is stored elsewhere?

I assume what you mean is that the login dialog is still displaying the
previous username. That will always be so.

The first time you implement security, the dialog picks up the Windows
username. Any subsequent sessions will always pick up the previous Access
username.

It doesn't mean that the user exists in the current mdw being used.

 

[Guest]

OK - thanx a million

Rip

I assume what you mean is that the login dialog is still displaying the
previous username. That will always be so.

The first time you implement security, the dialog picks up the Windows
username. Any subsequent sessions will always pick up the previous Access
username.

It doesn't mean that the user exists in the current mdw being used.