Automatic back-end back-up

[Guest]

Keeping in mind I only want to have a back up for the data in the tables, I
have a procedure that:

When a user opens their front-end, a function checks the date in a table in
the back-end; if the date equals the date in the table or is an earlier date
then the date in the table is updated to the next backup date and:

Using ADO create a new blank DB used for back up in a specific folder for
that purpose. Also using ADO/SQL all the tables are copied from the back-end
DB to the back-up DB.

Another sub routine loops through the files in the back-up folder and
deletes the Nth oldest one.

The DB I have is small, six stand-alone tables with no more than 100 rows
each and will not ever grow much more than that. This procedure seems to run
great and takes less than a second. Given that the complexity and size of the
DB does not grow, does anyone see any problems with this method?

Any and all input encouraged.

 

[Guest]

Hi XP,

Why are you doing this? You could simply include the back end data file in
your backup schedule for the server it lives on.

Damian.

 

[Guest]

Hi Damian, if I didn't have a good reason, trust me, I wouldn't be working on
it.
Our recovery time is terrible, that's why. I want to be able to bring the
users back up fast if there is a failure or corruption.

Now for real issue, what about the approach?