Access program renaming because of some error

[pgoulet]

Has anyone seen a situation where the Access program “DB1” may fail (as a result of some unknown reason, network problem possibly) and a duplicate file “DB2” is created.

If that has been seen, is it also the case that if the Access program name was something other than the default (DB1), would program <filename> become program <filename1>.

Thanks

Paul

 

[WayneRyan]

Paul,

When you do a compact/repair operation on a database,
call it test.mdb, Access will create a new empty
database called db1.mdb. It will export all objects to
it. If successful it will &quot;kill&quot; test.mdb and rename
db1.mdb to test.mdb. If the operation fails it will just
leave the db1.mdb there. The db1.mdb &quot;MAY&quot; be a viable
database.

If in the same scenario there was a pre-existing db1.mdb
Access will use db2.mdb (or 3, 4 ...).

If you were using a db1.mdb (not a good idea) and a
compact/repair failed you would have the &quot;extra&quot; db2.mdb.

hth,
Wayne

 

[pgoulet]

Thanks Wayne

Soo...

If I had several MDBs in the same network shared directory, and had a compact and repair failure, I could possible have DB1, DB2, DB3, DBx with each being related to it's parent MDB.

equipment.mdb
hotties.mdb
cars.mdb
contacts.mdb

What is the best way to handle several MDBs on a network, separate directories?

Paul

 

[WayneRyan]

Paul,

The locations, in general don't matter. The presence of
one of those &quot;dbn.mdb&quot; files indicates that something is
wrong.

When a person compacts a database, and an error condition
occurs, they should address it right then. Whatever it
is must be remedied before resuming normal business.

Sometimes the db1.mdb that is created is indeed a viable
legitimate database. Some inspection of it can confirm it.
If it really is, and please be sure, you can rename it
to the production name.

If it isn't then you must either fix the old (current)
one or rebuild it. Sometimes creating a new, empty
database and then using:
Files --> Get External Information --> Import
to populate it works.

The presence of db1.mdb thru db2.mdb can indicate that
someone is just ignoring these errors.

Additionally, if someone is saving a new database and
points to that directory, Access will assign it a default
name of dbn.mdb.

Looking at them should give you a clue.

Wayne

 

[pgoulet]

Thanks Wayne, some good pointers there.

Paul