Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Backup function from Access, backup linked tables?? 1

Status
Not open for further replies.

wavyak

Technical User
Mar 4, 2007
3
NO
I appreciate the new backup function in 2003, but it doesn't backup my data in the linked database, only the current db (which is the program).

I would like to backup my data (from the linked db) when I quit the application using "Application.Quit".

Have any of you any ideas of how to do it?
 
If the source of the linked tables is another Access database, there are a couple of options:
1. Copy the MDB or MDE file to an alternative location.
2. Generate the remote tables locally and copy the data into the front end (not a good idea mixing program and data).

If, however, the data are in a client/server database such as SQL Server or Oracle, you have the second option plus a third:
copy the data from the current database to another database. This can be done by running some SQL statements on the server to do the copying.

John
 
I do not want each user of the system to have to copy anything "manually". I want to program the end of the application in a way that makes it easy and natural (automatically) to take a backup, without using the menus in Access or using Explorer.

It is normal to split the data and the program in two different mdb's, why isn't it a facility to backup the data-mdb in a similar way as the current mdb, the program? The program is backed up after being compressed and saved with a date attached to the filename. That's nice, but it's the wrong db!

Are there some funcionality in Access 2003 that I've overseen? Are there any other solutions?
 
I don't do that much work with Access 2003, but it is certainly possible to have your frontend program copy the data MDB from one location to another.
Look at Scripting.FileSystemObject or the Shell command for two ways of performing file copy operations from within Access. Its not someting that you will need to train your users to do at all.

You may find though that you need to ensure that all of the tables, queries etc are closed, or you get messages about being unable to obtain exclusive access to the file when trying to perform the copy.

John
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top