I users are able to even open your database using their default system.mdw,
then you missed a step in securing it. Likely the Admin user still owns
object(s), and/or the Users Group still has permissions to object(s). Did
you use the security wizard?
Once you have it secured properly, you can put the mdw on the server, and
provide a shortcut. The shortcut requires the full path to msaccess.exe as
in,
"path to msaccess.exe" "path to mdb" /wrkgrp "path to secure mdw"

Signature
Joan Wild
Microsoft Access MVP
> Greetings,
>
[quoted text clipped - 14 lines]
> CAN ANY ONE HELP ... THANK YOU AND I APPRECIATE YOUR
> COOPERATION
Eng. Nader - 26 May 2004 10:10 GMT
Thank You very much,
I just wanted the command line form as your typed it:
("path to msaccess.exe" "path to mdb" /wrkgrp "path to
secure mdw")
because in Access Help it doesn't tell you to put the .exe
path ... but now after trying it your way it's working
100% ...
Thank you sooooooooooooooo much :) ...
>-----Original Message-----
>I users are able to even open your database using their default system.mdw,
[quoted text clipped - 27 lines]
>
>.
Joan Wild - 26 May 2004 15:26 GMT
Well you still have a problem. Although they use your workgroup file by
opening it via the shortcut, if they don't use the shortcut they are using
the standard system.mdw workgroup. You said they could get into your mdb
doing so.
If you secured it properly, they will *only* be able to get in using the
shortcut.

Signature
Joan Wild
Microsoft Access MVP
> Thank You very much,
>
[quoted text clipped - 52 lines]
> >
> >.