Access 2000 security issue

I hope someone can help me out set up the security properly.



I have Microsoft Access 97 and Access 2000 in my computer and I developed my
database with Access 2000 with the updated patch SP-3.



I had no trouble to create a workgroup and successfully to run the security
wizard and the group permissions. Everything seemed to work fine as expected
as long as both mdb and mdw files were in the same folder.



Unfortunately, the problem came up when I renamed or moved the folder and
did not join the workgroup to the specific folder. There would be no more
log-on prompt when I opened up the database. In order words, people would be
able to make a backup copy and open it up in any computer with the default
(or any) workgroup file.



I checked the default user group and the permission had been completely
removed (after running the security wizard). The default admin account was
no longer with the admins group.



I even followed Microsoft recommendation to create a new empty database and
import all objects from the secured database in order to work around the
security issue with the Access 97. So far, none of measures was successful.



Anyone can shed the light on the issue?



Thanks


.

Relevant Pages

  • Re: Access db accessibility (permissions??)
    ... if you have not then your computers are workgrouped, security becomes a bit ... password when you first login to your database. ... > folder and then delete it. ... So the permissions are RWED on that folder. ...
    (microsoft.public.access.security)
  • Re: database protection
    ... to share that folder with full permissions. ... database is at stake, anybody from any netwark location can damage the ... That should be enough to keep most casual snoops out, but if any of them are Access savvy then you might want to consider applying user level security. ... make BACKUPS of you files first, it's easy to lock yourself out when you're learning ULS. ...
    (microsoft.public.access.security)
  • Re: Design question!, uploading documents to webserver
    ... Storing pdf's in the db doesn't seem to resolve the security issue, since it leaves all access through your web application, and the web application has to handle the security. ... If the app is doing that anyway, you could store the docs in a folder that no user has access to, and let the app provide the docs on request. ... Documents will be in .pdf format. ... Documents will not be stored in database but instead uploaded to a folder on the webserver. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: setting a password on a button on the switchboard
    ... Could you send me the sample database for the fourth option (4. ... > Security in an Access database can probably be broken down into two big ... > points about being easier than User Level Security, ... > What type of data are you trying to protect? ...
    (microsoft.public.access.forms)
  • Re: access 2003
    ... security in access 2003. ... The data will go on the server and the program database ... than the alternative of creating an mde file. ... MDW file from the written record. ...
    (microsoft.public.access.conversion)