Hi Mirel
Two main comments for you. #1 is if you find that there is no security
on the "secured" db when you're using the out of the box system.mdw, you
haven't secured the database properly. #2 the shortcuts must not only
reference the db that you wish to run with the secured mdw, they must
also reference the secured mdw. But item #2 is more or less irrelevant
till you deal with item #1.
There is an Access security FAQ 'out there' that while not great is
perhaps the best starting point to getting a handle on how you can
secure an Access mdb. You can access it at
http://support.microsoft.com/default.aspx?scid=%2Fsupport%2Faccess%
2Fcontent%2Fsecfaq.asp
In article <1132879733.447984.47320[ at ]o13g2000cwo.googlegroups.com>,
mirel.rusu[ at ]freightlink.com.au says...
[Quoted Text] > Hi there,
>
> I've created a secure db in access 2003.
> When I join the the workgroup security.mdw, the security I've put in
> place works all right. when open it asks for password, doesn't allow
> the user level to modify, etc.
> however when I try to open a different database the security window
> appears and the security rutine restarts, which would be fine if I'd be
> the only one to work with access but some of the users with restricted
> access once joining the security.mdw they can't create or modify other
> db...
> I've read I need to create shortcuts on desktop for the secure db and
> for the "normal" db, and doing that didn't change a thing.
> If I'm on system.mdw there is no security for any db (including the
> "secure" one), if I'm on security.mdw all db I open become secure.
> Any help ?
>
> Cheers
> Mirel
>
>
|