Copy a DB while in use

[Dave]

Access 2007

Is it save to make a copy of database while in use?

Is the answer the same if it is a split DB and you make a copy of the
backend while in use.

thanks

dave

 

[Rick Brandt]

Access 2007

Is it save to make a copy of database while in use?

Is the answer the same if it is a split DB and you make a copy of the
backend while in use.

Depends on your definition of "safe". No one will be injured and the
original file will not be either. The question is will the copy be a
"good copy"? The answer is "usually", but it is less likely than if a
copy were made while it was not in use.

In a split DB you can close everything that is connected to the back end
and then it will not be in use when you copy it (assuming no other users
are in there).

 

[Dave]

Thanks for the quick reply Rick.
In either case it is possible that more then one user could be in the DB
The DB has not been split yet but will be soon (hence the question for both
scenarios)

The coping would be done by a batch file coping either the full DB or the BE
(after it is split).

It was a concern about the original file (or original BE)

glad to hear no on will be injured

dave

 

[Larry Linson]

But, what would be the point in copying if you suspected that the copy
wouldn't be any good? If there is activity in progress, there is a good
chance that the copy will be useless.

Larry Linson
Microsoft Office Access MVP

Thanks for the quick reply Rick.
In either case it is possible that more then one user could be in the DB
The DB has not been split yet but will be soon (hence the question for
both scenarios)

The coping would be done by a batch file coping either the full DB or the
BE (after it is split).

It was a concern about the original file (or original BE)

glad to hear no on will be injured

dave

 

[Dave]

Purpose of the "copy" is that we had one incident of the whole DB
disappearing.
I had a backup so they only lost one day of work.
But that is too much
These are seriously challenged "file Management" users.
If I allow the "boss" to run the back up batch file at her whim, I am hoping
at least one of the reasent files will be good.

IF the response is that we have a great percentage of the "copies" being bad
than I need another approach.

That's why I am asking for help

Thanks for the reply

dave

But, what would be the point in copying if you suspected that the copy
wouldn't be any good? If there is activity in progress, there is a good
chance that the copy will be useless.

Larry Linson
Microsoft Office Access MVP

 

[pietlinden]

Purpose of the "copy" is that we had one incident of the whole DB
disappearing.
I had a backup so they only lost one day of work.
But that is too much
These are seriously challenged "file Management" users.
If I allow the "boss" to run the back up batch file at her whim, I am hoping
at least one of the reasent files will be good.

IF the response is that we have a great percentage of the "copies" being bad
than I need another approach.

That's why I am asking for help

Thanks for the reply

dave

How about running some code to kick out all the attached users and
then running the backup? Arvin has code to kick everyone out... then
backing up should be trivial.