> Hi there
>
[quoted text clipped - 6 lines]
>
> What am I missing here?
You missed a step in securing it. Either the Admin user still owns the
database, or the Users Group has permission to objects.
> I am using a shortcut string to initiate accessing the secured
> database. The Database is although not joint with the system.mdw, but
> with mysytem.mdw, which causes that if I want to open any other
> database, which I thought are not joint with the mysystem.mdw are
> requiring all of its sudden passwords too!!!
Databases are not joined to a workgroup file. The workgroup used is session
based. Every time you start Access it uses a workgroup file - even for
unsecured databases. It uses whatever workgroup you are currently joined to
by default. Out of the box, it silently logs you in as Admin using the
system.mdw workgroup. That is why, since you are joined to mysystem.mdw,
you are getting a login prompt for every database.
Leave your computer joined to system.mdw and use desktop shortcuts to start
your secure databases. The shortcut can include the /wrkgrp switch which
will override the default mdw for just that session of Access.
Follow the steps in
Security FAQ
http://support.microsoft.com/?id=207793
I've also outlined the steps at www.jmwild.com/AccessSecurity.htm

Signature
Joan Wild
Microsoft Access MVP
Norman Fritag - 12 Aug 2004 21:40 GMT
Joan,
thank you!
Regards Norman
> > Hi there
> >
[quoted text clipped - 32 lines]
>
> I've also outlined the steps at www.jmwild.com/AccessSecurity.htm
Denny - 19 Aug 2004 05:01 GMT
Hi all,
I am stil not clear how to achieve this.
It's true that you can make your database secure through shortcut.
But other user on the network can always access the database straight
to the .mdb file.
In this case they will use their own "default" workgroup file and
still able to make changes.
Am I missing something here?
Many Thanks.
Regards,
Denny
Joan Wild - 19 Aug 2004 13:47 GMT
> Hi all,
>
[quoted text clipped - 6 lines]
>
> Am I missing something here?
Yes. If they can even open your database using their own default workgroup
file, then you missed a step in securing it.
Check that the users group has no permissions to anything (check the
database object). Check that the Admin user doesn't own any objects. Those
are the two most common reasons.
If you implement security, following *every* step, your users will not be
able to open the mdb without using the correct mdw file.

Signature
Joan Wild
Microsoft Access MVP
Denny - 25 Aug 2004 03:07 GMT
Thanks Joan,
I've redone the steps and made it works!!