G
Guest
I have an Access 2003 database split into front-back ends. The back end is on
a server. Once a week I perform a Compact and Repair on the back end. This
time, however, I get an error message that Microsoft has encountered a
problem and needs to close. I am them prompted to save it and try to repaoir
the open database, but that doesn't work wother. I end up in a loop-- name
the backup, then get an error message, then name another backup , then get
another error message, etc.
I tried moving the back-end to my local driver to see if that would work--
no dice, same error message. The back end has swelled to about 53 MB (it
should be about half that). It still seems to work, but I'm getting very
nervous.
What can I do? Any ideas? THanks.
a server. Once a week I perform a Compact and Repair on the back end. This
time, however, I get an error message that Microsoft has encountered a
problem and needs to close. I am them prompted to save it and try to repaoir
the open database, but that doesn't work wother. I end up in a loop-- name
the backup, then get an error message, then name another backup , then get
another error message, etc.
I tried moving the back-end to my local driver to see if that would work--
no dice, same error message. The back end has swelled to about 53 MB (it
should be about half that). It still seems to work, but I'm getting very
nervous.
What can I do? Any ideas? THanks.