Link to home
Start Free TrialLog in
Avatar of Fritz Paul
Fritz PaulFlag for South Africa

asked on

Auto backup on every change

I am making some changes to an Access 2003 database front end on a client's computer. He runs Access 2007 on Windows XP.

Every time I make a change the system makes a backup copy of the front end, which is around 90 MB. This easily takes a minute and I have to wait for that process before I can move on.

When I install on my machine, it does not make a backup each time and there is no waiting time.

There must be a setting on the client's machine that causes the backup, but I do not seem to find it.

Any pointers?
Avatar of peter57r
peter57r
Flag of United Kingdom of Great Britain and Northern Ireland image

It's not an Access setting.
It must be something to do with the clients machine config.

You would need to look at what disc management software/backup software is being used.

I think there are several products around which create backups on any change to nominated files, but I don't know of anything built in to Windows (that doesn't mean there isn't of course)
Avatar of Fritz Paul

ASKER

Thanks so far.
I will leave the question open to see if I get any other pointers.
I have now made an appointment with the system administrator in a few hour's time and will take up with him.
Avatar of iaintarr
iaintarr

Hi there,

This is not necessarily a configuration of the DB.
You may have issues with the data access from your access version when accessing the data in the backend.

Have you tried using Access 2007 as the front end instead of 2003?
Have you tried access the data directly via the backend copy?

In versions of access, when an error occurs, it automatically shuts and opens up a new copy with Recovered or Backup as an appendage to the file name.
Although the client runs Access 2007, I have been hesitant to convert the front end to 2007 They have an extended switchboard, which was created with access switchboard manager and I am afraid to lose that. They also use access 2003 security, which I also believe will be lost with Access 2007.
From what the two of you have said, I believe the issue may be solved if they upgrade to Windows7.
I think we should perhaps try that.
Access is a file based db, and the front end is no different.
Why dont you create a backup copy of both and test without affecting the production versions?
Dont tinker on the live versions if you can help it.
ASKER CERTIFIED SOLUTION
Avatar of peter57r
peter57r
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thanks for all support.
When I was at the client site today, with the sytem administrator, the issue did not appear again. The past three days I battled with it every day.
PROBLEM DECIDED TO MOVE ON.
I hope I never meet it again, even if I never find out what was wrong.
But I found the advice that you EE people gave me very helpful.