Marco said:
yes, I think you are understanf my point of view.
My back end is in a shared folder witch is in a server. I know that
is I can join that database do an MDW but if another person try to
opin in a different computer he can open.
If that's the case, then you missed a step in securing it. That other
computer is joined to system.mdw (the one that ships with Access) by
default. Therefore, they should not be able to even open the database.
Since they can, you missed a step. Likely the Admin user still is owner of
objects, or the Users Group has permission to something.
The Admin user should not own anything, and the Users Group should have no
permissions to anything.
If you have a backup of your mdb, before you started security, restore it
and try again. Be certain that you follow *every* step.
Security FAQ
http://support.microsoft.com/?id=207793
Security Whitepaper
http://support.microsoft.com/?id=148555
Although the whitepaper is old, it contains information to help you
understand security.
I've also outlined the detailed steps at
www.jmwild.com/AccessSecurity.htm
Did you understan? I even try, to insert a password to open the
backend, but then it returns me a error.
You can put a password on the backend, however you then need to delete the
links in the frontend and then recreate them. You'll be prompted for the
password when you recreate the links, and then get no error. Keep in mind
though, that the database password is quite weak and easily hacked.