Data Files Left Behind on Network

[Thems]

I have a small peer to peer network with all computers running XP Pro w/ SP3 and Access 2007. The issue only started when Peer A upgraded to Access 2007 from 2003.
The issue is, when Peer A opens a data file call - SDA.mdb on Peer B’s computer and closes access, a file is left behind in Peer B’s called database.mdb (file size is very close to the SDA.mdb file size but not exact). When the file is accessed multiple times, multiple files are created and left behind – database.mdb, 1database.mdb, 2database.mdb, 3database.mdb, and so on. This happens whenever Peer A opens any other peer’s data file.

If Peer B or Peer C opens another peers data file, including Peer A, this does not happen. The database.mdb file is created but deleted when Access is closed.

This does not happen when Peer A opens data files on there own computer, only over the network.

I converted the SDA.mdb to a SDA.accdb file to see if this made a deference, but the database.mdb files are still left behind.

[Jim Doherty]

I have a small peer to peer network with all computers running XP Pro w/ SP3 and Access 2007. The issue only started when Peer A upgraded to Access 2007 from 2003.
The issue is, when Peer A opens a data file call - SDA.mdb on Peer B’s computer and closes access, a file is left behind in Peer B’s called database.mdb (file size is very close to the SDA.mdb file size but not exact). When the file is accessed multiple times, multiple files are created and left behind – database.mdb, 1database.mdb, 2database.mdb, 3database.mdb, and so on. This happens whenever Peer A opens any other peer’s data file.

If Peer B or Peer C opens another peers data file, including Peer A, this does not happen. The database.mdb file is created but deleted when Access is closed.

This does not happen when Peer A opens data files on there own computer, only over the network.

I converted the SDA.mdb to a SDA.accdb file to see if this made a deference, but the database.mdb files are still left behind.

Make sure the 'Compact on Close' option is not selected. Compaction copies the file and should destroy but sometimes it doesn't.

[missinglinq]

This is almost sure to be the problem, as Jim has said, and using Compact on Close' is, in my opinion, a very bad practice! Over the years I have seen dozens and dozens of reports of chronic data corruption caused by compacting a database. Because of this, you really should make a back up copy of a database before performing compacting it, and using the "Compact on Close" doesn't allow for this.

If you insist on using "Compact on Close" here's a link to the hotfix that fixes the problem:

http://support.microsoft.com/kb/949404

Welcome to Bytes!

Linq ;0)>

[Thems]

Thanks Guys

That fixed the problem and thanks for the warning on "compact on close". I am turning that option off on all computers right now.