I'm attempting to put a CompactData

[Capgard]

I'm attempting to put a CompactDatabase routine in my app, but am experiencing some issues with the permissions necessary to run the CompactDatabase method. After trying many different permissions, the only time I was able perfom the compact successfully was if the Userid I specified was either (a) the Owner of the source database or (b) belongs to the Admins group. All the other userid/groups that didn't work had the same permissions assigned.

For example...
The owner userid is assigned to 3 groups, none of which was Admins, and this worked.
A userid assigned to only Admins and Users worked.
A userid assigned to all three groups that the owner was assigned to didn't work.

Since I want to embedd this id and password in the application, I don't want to expose the owner userid or a userid with Admins permissions to potential cracking from within the application. I would really like to create and ID/Group that will only perform the Compact and nothing more.

Any suggestions and/or insight?

TIA
Capgard

 

[Terpsfan]

1. I wouldn't fool with Access security...I find it nearly useless. If you have several databases, then you have to have several system.mdw files running around and it createse a royal mess. I create my own security with logons and passwords and put the information in a local table. I usually split the database and create an mde so the code is invisible to the user. The users can't delete tables, only the links to the tables. Users can create their own queries but can't create new forms, reports nor can they delete the existing ones. I find creating an mde to be just as much security as Access security. Plus Access security is a bottleneck that slows the application down.

2. I would designate one or two people to be able to compact, backup, restore the database. Run the compact database routine without the security on a form.