Created security - now ALL databases have this security

  • Thread starter Thread starter Jennifer
  • Start date Start date
J

Jennifer

I've secured a database but now every database I create
has this security. I don't want this. I've read through
the other posts and found where Lynn has said to "join the
default system.mdw file using the workgroup administrator
and use a shortcut with the /wrkgrp switch to open your
secured databases"

I'm sorry but this is totally Greek to me. I know just
enough about Access to create this database and I'm afraid
I got in over my head. I have no other database files for
this original database because I had thought to start over
and deleted them all - including the .bak file, etc. Anny
suggestions?
 
Ok, perhaps I've figured out my own problem. Can someone
advise me if I've done right or wrong? I've created a new
Workgroup Admin... so far, it seems to have solved my
problem. However, any advice as to whether or not I did
this wrong would be appreciated.

Thanks!
 
Jennifer said:
I've secured a database but now every database I create
has this security. I don't want this. I've read through
the other posts and found where Lynn has said to "join the
default system.mdw file using the workgroup administrator
and use a shortcut with the /wrkgrp switch to open your
secured databases"

I'm sorry but this is totally Greek to me. I know just
enough about Access to create this database and I'm afraid
I got in over my head. I have no other database files for
this original database because I had thought to start over
and deleted them all - including the .bak file, etc. Anny
suggestions?
Click to expand...

Access user-level security is not "per file". It is "per session" and
whether you get a logon prompt or not is determined by the workgroup file
being used for that session, not by the file or files you might attempt to
open.

If your level of expertise is as you say then stay away from security for
the time being. It is easily one of the hardest areas of Access to fully
understand and use correctly. IMO opinion it was a mistake for MS to even
supply a wizard for this because it allows people to implement something
very complex without having the first idea of how it works under the hood.
 
Open Access (no database). Go to Tools, Security, Workgroup Administrator.
Click on Join and rejoin the system.mdw that ships with Access. I tusually
is in the windows system folder, but you could search for it first using
Start, Search, Files or Folders.

If you deleted all the files including the bak file, then you now have no
copy of your database.
 
-----Original Message-----


Access user-level security is not "per file". It is "per session" and
whether you get a logon prompt or not is determined by the workgroup file
being used for that session, not by the file or files you might attempt to
open.

If your level of expertise is as you say then stay away from security for
the time being. It is easily one of the hardest areas of Access to fully
understand and use correctly. IMO opinion it was a mistake for MS to even
supply a wizard for this because it allows people to implement something
very complex without having the first idea of how it works under the hood.


--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com


.
Click to expand...
Actually, I followed the instructions on Lynn's website
and was able to fix my problem and secure the database.
Thanks Lynn!
 
Back
Top