Database automatically creating a back-up file

  • Thread starter Thread starter Emma
  • Start date Start date
E

Emma

I have created a database which is used by mulitple users
across a network. And for some reason automatically a back-
up file of the whole database is created.

I would like to stop this happening as at the moment I
have 3 back-up files created, and they are causing some
confusion.

If someone could let me know how I can stop these being
created it would be much appreciated.

Thanks
 
Emma said:
I have created a database which is used by mulitple users
across a network. And for some reason automatically a back-
up file of the whole database is created.

I would like to stop this happening as at the moment I
have 3 back-up files created, and they are causing some
confusion.

If someone could let me know how I can stop these being
created it would be much appreciated.

What do you mean? What do the names of these backup files look like?
If it's "db1.mdb", "db2.mdb", and so on, it's probably the result of
failed attempts to "Compact on Close" (which is an application option).
The failure may be due to one of the users not having the necessary
network permissions on the folder containing the database -- they must
have full permissions: read, write, create, and delete.

Are all users working directly on the same, un-split .mdb file on the
network drive? That arrangement can work, but it is susceptible to
corruptions. If that's what you're doing, you should consider splitting
your database into a front-end file (forms, queries, reports) linked to
a back-end (tables only), put the back-end on the server, and give each
user her own copy of the front-end.
 
Back
Top