I'm using Windows XP, SP2, and when I right click on a file and select Properties, one of the Attributes is Hidden ...
perhaps this would work for what you want? Of course, if users are allowed to manipulate their machine settings they can
tell Explorer to show hidden files, so this may not work for all users.

You can also rename the file to whatever you wish (something like bmcwln.dll or something equally odd). Access doesn't
care what it's named, after all, and users would be far less likely to click on those files (at least in theory).

Your other post indicates that you're trying to "secure" your database, without using ULS. While ULS has it's flaws,
it's still the best method to use to keep users out of your application.

Scott McDaniel
scott@takemeout_infotrakker.com
www.infotrakker.com

You need to remove 'browse' permission from the file.

Get IT to remove inheritable browse permission from the
folder as well, so that when you compact the file you don't
loose the permission setting.

Check this anyway after doing a compact/repair, because
some versions incorrectly inherited their permissions from
the users temp folder.

For best efficiency, the folder should be as near to the root
of the drive as possible, and there should be a share directly
on the folder. Users should have the "Bypass traverse checking"
privilege.  SMB packet signing should be turned off on the file
server.

(david)

Any techniques you can try can likely be broken somehow.   If you
truly require rock solid security, such as a legislated requirement,
then I'd suggest moving to SQL Server.

Tony