How to create Periodic backup in Ms Access

[javedsai]

Hi,

I need to build a functionality which can take backup of my database periodically, i.e. admin must able to set the timer in how many days he wants to run database backup. For example, If admin set 2 days then, in every 2 days it must create database backup whenever the Ms Access is open. Kindly, suggest.

Thanks in advance.

[GazMathias]

Why not create a simple batch file to copy the .mdb and set a scheduled task in Windows to run the batch file every x days?

Google dos batchfile

[missinglinq]

Gaz' approach is the way to go, keeping in mind that the database ***has to be closed*** at the time the copying is done! Trying to copy an open Access database is an invitation for data corruption.

Welcome to Bytes!

Linq ;0)>

[youmike]

If you are running a split database, i.e. front end with everything except the data and only data in the back end, my experience is that running a batch file to copy is not a problem.

I have one customer where we run several scheduled tasks at differing intervals - hourly, daily and weekly in this particular case - we had to use a backup the other day to deal with a power interruption issue and there were no difficulties.

As I said in another post, back-up set should include several folders (I simply number mine, 1 being the newest and thereafter 2, 3, 4 - as many as necessary) and the batch file should delete the oldest of the set, rename the others and create a new folder called 1, into which any files to be backed up are copied.

All of this assumes that you have knowledge of the DOS commands which have to be incorporated into a batch file. The switches associated with the DOS commands are important and can be accessed from the DOS command prompt. A disadvantage of this approach is that there is no file compression. This could be got round by having the scheduled task run a parameter driven compression program.

If anyone feels a need, I could post a sample batch file with comments.

[javedsai]

If you are running a split database, i.e. front end with everything except the data and only data in the back end, my experience is that running a batch file to copy is not a problem.

I have one customer where we run several scheduled tasks at differing intervals - hourly, daily and weekly in this particular case - we had to use a backup the other day to deal with a power interruption issue and there were no difficulties.

As I said in another post, back-up set should include several folders (I simply number mine, 1 being the newest and thereafter 2, 3, 4 - as many as necessary) and the batch file should delete the oldest of the set, rename the others and create a new folder called 1, into which any files to be backed up are copied.

All of this assumes that you have knowledge of the DOS commands which have to be incorporated into a batch file. The switches associated with the DOS commands are important and can be accessed from the DOS command prompt. A disadvantage of this approach is that there is no file compression. This could be got round by having the scheduled task run a parameter driven compression program.

If anyone feels a need, I could post a sample batch file with comments.

Please post it. It will help me.

[youmike]

Will; try to do in next 24 hours

[youmike]

This batch file assumes that there are three generations of backup files,
numbered 1, 2, 3 in a folder called “Backups” on the “F” drive of a network machine called “Server”.
These folders must be created before running the batch file.
It also assumes that all data to be backed up is in a folder called “Data” on the “D” drive of a local machine
In any batch file, any line that starts with a colon(:) is treated as comment.
Such lines are not processed

: START OF DOS INSTRUCTIONS
rd /S /Q \\Server\F\Back ups\3
ren \\Server\F\Back ups\2 3
ren \\Server\F\Back ups\1 2
md \\server\F\Back ups\1
xcopy D:\Data \\Server\F\Back ups\1 /S /E /C /F /K /Y
ATTRIB -H -R -S \\Server\F\Back ups\1
: END OF DOS INSTRUCTIONS

Notes regarding customising
All changes must be exactly right Typing errors are the biggest cause of problems when writing batch files.
File and folder names should be changed to suit your local requirements

[javedsai]

Thx Guys,

I'm doing R&D on Batch files. Very soon I'll get back to u.

[NeoPa]

Strangely enough, I was just over in Windows talking about Batch files (or, as I recommend, CMD files).

I would (nearly) always recommend using CMD files rather than BAT files nowadays (since the early to mid noughties actually) though. Since the demise of Windows 98 (ignoring ME) all Windows based operating systems have been versions of Win NT, and so run the CMD.Exe command interpreter as well as the much more limited Command.Com version (compatible with all older versions of Windows as well as DOS).

In almost all situations BAT files run seamlessly in the CMD.Exe command interpreter.

[javedsai]

I tested batch files its working fine. But, my client told me that he want something which can be incorported by Ms acces i.e. I don't want any extra files. I want everthing with Ms Access itself.

I want to develop an application which should be user friendly. i.e Once I delivered my application then I don't want to give any kind of support to user/client. Thats why I required functionality through which user can set time and on that particular time system must take back up of my application.

For this purpose I'll be having interface where user can set time then, at that particular time system must take back up of application. Is there any other method then, plz suggest but, I don't want any extra or external file.


Note:- I don't want any extra file.

Thank you...