Unwanted Automatic Backup

[Brian_M via AccessMonster.com]

Hi folks,

This is kind of a strange problem to have. The database we use for our
inventory/etc is creating backups apparently on its own. The initial db is
named PNCINV.mdb. Every time a change in a table happens, and then the
database is exited, it creates a backup in the same directory named Database.
mdb. If the process is repeated, it renames that one to Database1.mdb, then
backs up the current one again with the name Database.mdb.

It's kind of like it's making a whole database backup after closing the
database if a transaction was made. Needless to say, it is pretty rediculous
to have that many backups, and because it is on a network, multiple users
make changes etc...so there gets to be a considerable number of backups.

I could not find any code anywhere that would explain this behavior (I did
not make this database--I hate it and have been rebuilding it anew, but this
is still the current one.)

Any suggestions?

 

[Joan Wild]

Check under Tools, Options that 'compact on close' is unchecked. It is possible that the last person out of the database doesn't have delete permission on the folder, so is unable to delete this database during the compact process. You should do compacting separately.

In addition, you should split the database so that each user has a copy of the frontend on their PC, linked to the tables in the backend mdb on the server.

More on splitting at
http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

 

[Brian_M via AccessMonster.com]

I have permissions to delete on the server, and have taken ownership of the
database so I know I have permissions to do whatever with it. I hadn't
considered that compacting on close would cause problems like that, however.
I plan to split the new database when I'm finished with it and distribute
that as needed; for now, I'll just manually compact the current db as
necessary.

Thanks!

Brian

Check under Tools, Options that 'compact on close' is unchecked. It is possible that the last person out of the database doesn't have delete permission on the folder, so is unable to delete this database during the compact process. You should do compacting separately.

In addition, you should split the database so that each user has a copy of the frontend on their PC, linked to the tables in the backend mdb on the server.

More on splitting at
http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

Hi folks,

[quoted text clipped - 15 lines]

Any suggestions?