Backing Up Data

ddrew

seasoned user
Local time
Today, 23:14
Joined
Jan 26, 2003
Messages
911
Could someone give me some advise on Backing Up data.

My intention is to split the database, but want the user (single users) to be able to backup their data to a memory stick so that it can be resinstalled on a new PC if required or if I should create an update for the software.

Should I back up into EXCEL or just copy the back end of the DB (Tables) complete to a destination of the users choice?
 
If you are on a LAN then the Backend should reside on the Server where it should be backed up regularly

As an added feature you could copy the whole file to a USB or anywhere else you want.
 
Last edited:
If yyou are on a LAN then the Backend should reside on the Server where it should be backed up regurally.

As an added feature you could copy the whole file to a USB or anywhere else you want.

Its not going to be on a LAN its on a numbe rof individual PCs holding information about their own dogs.

I appreciate that I could copy the whole file, but I only realistically need the tables in order for the user to import the data after a potetial update.

Im also reading from other threads that its best to back up to a different format either excel or txt.
 
Im also reading from other threads that its best to back up to a different format either excel or txt.

I don't know where you got that info as it is not correct.

Just copy the whole file. It is the easiest, fastest and safetest.
 
OK, but right now the DB isnt split so do I have to stipulate which parts of the DB to copy or should I leave the buuilding of this until I have split the DB
 
Im also reading from other threads that its best to back up to a different format either excel or txt.

It could be useful to backup the data to a different format... if there's any hidden corruption in the Access db, this would be a good safeguard against that (it's possible you would run into a day where something goes wrong with the data, and going through backups you find that you can't access those either).

For general purpose though, I tend to copy the entire file myself.

Cheers,
 
OK, but right now the DB isnt split

So split it now.

Unless you have a reason why you can't.

As far as exporting to a different Format, you could write some code that will automatically export to an Excel Workbook. Each sheet would hold data for each Table.

But I would prefer to export to a new Database. If there is corruption then this type of export would most likely fail thus alerting you to a problem.
 
Also warn your users to be very careful when backing up to memory sticks/thumb drives, etc. Over the past six years, since I've been disabled, I've spent a good 6-8 hours a day cruising Access forums, and I've seen literally dozens and dozens of reports of corruption due to their use in backing up Access files! Apparently they have a bad habit of reporting that the data transfer is complete when, in fact, it requires a few more seconds to be complete. The reports are almost always when people are doing this to take home work to be completed on their home PCs. It appears that doing a simple 15-20 second count after the transfer is reportedly complete, before removing the drive, resolves the issue.

Linq ;0)>
 
missinglinq

What you said is another very good reason to eject the stick correctly rather than just pulling it out.
 
Absolutely! People are almost always getting ready to go home for the day and naturally in a hurry! :D

Linq ;0)>
 

Users who are viewing this thread

Back
Top Bottom