I am trying to secure an Access database at the file level per these
instructions at http://support.microsoft.com/default.aspx?kbid=208778
which summarize to:
Required Folder Privileges
If you plan to share a database, the .mdb file should be located in a
folder where users have read, write, create, and delete privileges.
Even if you want users to have different file privileges (for example,
some read-only and some read-write), all users sharing a database must
have read, write, and create permissions to the folder. You can,
however, assign read-only permissions to the .mdb file for individual
users while still allowing full permissions to the folder.

I want to do as that states - assign read-only permissions to the .mdb
file for individual users, but they need full permissions to the
folder.

I thought the way to accomplish this would be by using an Inherited
Rights Filter at the file level BUT it seems the problem with an IRF
on a file is that the setting will be reset when the file is recreated
(such as in a database compaction). Is this true?

What is the right way to secure the files/folders as outlined by
Microsoft?

Cayce