Backup copy in access

[avivit]

Is there a way to AUTOMATICALLY save a copy of access file (certain file or any file) in one directory after saving it in other directory.
I.e - I'd like to save an access file where I choose, and then I'd like to have a copy of it in a directory I'll choose in advance. I'd like the backup part to be automatic.

Thanks in advance

 

[sjn]

Two methods come to mind. The first method involves creating a front end procedure that provides the ability to copy the database before accessing it. You can then use a special file that give the parameters you require or use the opening arguments as the parameters for the copy.

The second method is somewhat similar to the first only that the command line arguments are used or a special file that indicates the backup parameters. Then you create a global module procedure that loops through all of the database objects that you want to back up and export them to the specified database(s).

The latter method also gives you the ability to only export the tables that have been changed from the previous export by comparing them with the objects that already exist in the backup table. You can also create version sets for each backup.

Scott.

 

[avivit]

Thanks Scott,
I think I prefer the 2nd method.
I'll search for a documentation of how to do it.
If anyone has one, I'll be glad to have the link to it.

 

[Quehay]

This would also be another way of improving LAN performance:
User works with a copy of tables on hard drive and then copies the changed tables over existing tables on the network at program close. I've been thinking about this one (don't know the method yet). A forseeable problem is the case of two users simultaneously trying to copy a new version of the table onto the network version.

If anyone has done this or something similar it would be great to learn!

 

[JerryDennison]

You may want to consider creating a Replica set. You can then syncrhonize the replicas whenever you'd like via code. It will not require copying files or tables which could overwrite changes/additions another user may have made.