Compacting "database name.mdb" creates "db1.mdb"

[Goobz]

Almost everytime I compact my MDB, which is usually somewhere around
5mb, it creates a db#.mdb, which is around 980kb. After decompiling
then recompiling, it ends up about 1mb.

It seems to be the same file, and all, but why does it create a
totally different filename!?

 

[Pete D.]

Could use more info, what version of access, is it on a network, what
version of windows.

 

[Goobz]

Could use more info, what version of access, is it on a network, what






- Show quoted text -

Sorry...

OS: Windows XP Pro SP2
OOS: Access 2003 SP3
Network: Yes. Stored on a network drive, but this has also happend on
my local copy before **if** I remember correctly...

 

[Jerry Whittle]

A simplification: Access first creates a new database called something like
db1.mdb then compacts everything into it. Next it copies db1.mdb to the old
database name. Lastly is deletes db1.mdb. That way if anything goes wrong,
you shouldn't lose a copy of the database as there are at least one and
possibly two copies of it.

However if something goes wrong or there's an error the original database
won't be lost and/or the db1.mdb won't be deleted. It's possible that
something is interferring with the C&R.

Another good possibility is that you don't have full permissions for the
folder holding the database files. For example if you don't have delete
permissions, the db1.mdb file won't be deleted.

 

[Pete D.]

What he said...Now Jerry, the # sign made me wonder if it was vista. Is
this something normal? Pete D.

 

[Goobz]

A simplification: Access first creates a new database called something like
db1.mdb then compacts everything into it. Next it copies db1.mdb to the old
database name. Lastly is deletes db1.mdb. That way if anything goes wrong,
you shouldn't lose a copy of the database as there are at least one and
possibly two copies of it.

However if something goes wrong or there's an error the original database
won't be lost and/or the db1.mdb won't be deleted. It's possible that
something is interferring with the C&R.

Another good possibility is that you don't have full permissions for the
folder holding the database files. For example if you don't have delete
permissions, the db1.mdb file won't be deleted.
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.





- Show quoted text -

This is very interesting.. I checked the rights on the servers folder,
and everyone in my group has Modify access (R/W/D).

I copied the BE and the MDB to my Thumbdrive, and re-decompiled, then
compacted, then recompiled, then recompacted, and I watched it make
the db1.mdb file, then once I said reopen, the db1.mdb file
disappeared.. That was quite interesting..

I've just never noticed those files appearing before today, when I was
auditing the databases on the server..

Thanx for the help folks...


CASE CLOSED!