How do I stop Access 2007 Making a Copy of Itself when Closing Application

is it the backup copy?
there is something wrong with your database if this is the case.

try doing compact and repair
Tools >Database utilities > compact and repair database

if problem persists,
* do a decompile
   see this link
http://www.granite.ab.ca/access/decompile.htm

* after that, create a blank db and import all objects
* open the VBA window and do
     Debug > Compile
     correct any errors raised

* do a compact and repair

Can you explain a little about this. How have you determined that it makes a copy of itself.

If there was a crash, access tries to recover and will prompt you for a name.

Are you looking in windows explorer? There will be two files, both have the same prefix but the suffix differs as one is a lock file. It gets removed when all connections to that database have ceased.

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

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.

So what are the names of these copies. Do they like have a standard naming convention? eg _Backup or something?

The Compact and repair only occurs on the database that the user directly opens, typically the Front-end database. Is this problem occuring on a Front-end or Back-end database?

Front end db

FB is the user copy on public data share

Copies that are generating  are uniform 1,2,3......naming conventions

Sorry that should read DB NOT FB

Is this something new, or has this always happened?

mx

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.

"access creates temporary data for a user and this may be the cause of the your problem. "

Ummm ... I don't think so.  And what 'temporary' data?

mx

Thanks. This has happened with 2007 and now with 2010.. I do not recall ever seeing in 2003 version.

We have used this method successfully for several years without too many issues.

Have you got any backup scripts?

"This has happened with 2007 and now with 2010.."
Are these ACCDB's or MDB's running the A2010 environment ?

mx

"read only copy of this db"
When you say 'read only', do you mean it's being open as Read Only?  If so, how. Or what exactly does 'read only' mean in this case, ie., how is that implemented.

mx

No backup scripts
Ms access DBS ... most were converted from 2003 but some are newly created in 2010

To clarify my read only description ... we do not give write permissions to DB files on the network share.  Folks just need to look at the DB not modify.

"we do not give write permissions to DB files on the network share. "
And has that also always been the case, even when this issue did not exist ?

mx

Yes  the permissions have stayed the same (no write) for several years

Thank you... none reported but I will c heck personally

This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.