Who is Participating?

Well, that's odd then, because I'm wondering how JET writes entries into the LDB file as users enter and exit ... since you have no Write permissions on this folder, if I understand what you are saying ... ?

Generally, when I see backup copies of a db as such, this happens when a user gets the 'Access Must Close Now, sorry for our bugs ... " message (aka a crash). In this message box, the is that check box that is by default checked, that says "Make a backup and reopen the db". Since users typically don't notice this, then a 'backup' is created, and the db reopens.

There’s a high demand for IT security experts and network administrators who can safeguard the data that individuals, corporations, and governments rely on every day. Pursue your B.S. in Network Operations and Security and gain the credentials you need for this high-growth field.

If you do not have permission to create a new file on a network folder and the database is set to "Compact and Repair" on exit, then you will get a new db1.mdb database when you exit. You will have to discuss this with the network administrator. There are some settings that control the permissions for a user for a specific folder.
Bob

0

bellezzaguruAuthor Commented: 2010-11-09

Access 2010 DB on a Windows 2008 R2 Server Share. Multiple users go into a read only copy of this db... even tho C/R is not checked the file makes a copy of itself upon exit of the DB ... it is taking up tons of space on the share... we have to watch it daily to erase the copies.

I don't think that you can set an mdb or accdb to read-only and expect it to truly be read-only. You may not be "writing" anything to the front-end mdb but access creates temporary data for a user and this may be the cause of the your problem.
It is never a good idea to share a front-end. This problem will likely go away if you give each user a copy of the front-end database. There are other challenges that you will need to address including distributing updates to the front-end but it will stop the problems with copies of the database.