compact and repair database

[Guest]

Our fiscal software is written in Access. Every day we compact and repair
the database and then back up the database from our server to a workstation.
We have had a problem occur the last few months. The software people think
it's a problem with our server but I wonder if it may be something with
Access, possibly as a result of one of the updates. Our version is 2003, SP
2.

When we try to compact and repair the database, we get an error and the
system changes the file name to dbl. I have to rename it in order to run the
program. The error message we get begins "Microsoft Office Access can't
delete [server:\foldername\filename.mdb] after compacting it. The compacted
database has been named [server:\foldername\dbl.mdb"

This occurs randomly but seems to be happening more often and we can't seem
to find a pattern. Any ideas?

 

[kingston via AccessMonster.com]

Are you compacting the database over the network? If so, you might consider
copying the file over to your local computer and then compacting from there.
Unless you have a really reliable network or a really small data file,
there's a lot of ways compacting over a network can cause problems (e.g. data
corruption that doesn't cause Access to throw an error message).

Our fiscal software is written in Access. Every day we compact and repair
the database and then back up the database from our server to a workstation.
We have had a problem occur the last few months. The software people think
it's a problem with our server but I wonder if it may be something with
Access, possibly as a result of one of the updates. Our version is 2003, SP
2.

When we try to compact and repair the database, we get an error and the
system changes the file name to dbl. I have to rename it in order to run the
program. The error message we get begins "Microsoft Office Access can't
delete [server:\foldername\filename.mdb] after compacting it. The compacted
database has been named [server:\foldername\dbl.mdb"

This occurs randomly but seems to be happening more often and we can't seem
to find a pattern. Any ideas?

 

[Guest]

I don't have an answer to that. All I know is that I open Access and the
file name is there and I proceed from there, but it doesn't give me the path
(don't know if it's server or workstation). At least we have something to
check now. Thank you.

Jonilyn

Are you compacting the database over the network? If so, you might consider
copying the file over to your local computer and then compacting from there.
Unless you have a really reliable network or a really small data file,
there's a lot of ways compacting over a network can cause problems (e.g. data
corruption that doesn't cause Access to throw an error message).

Our fiscal software is written in Access. Every day we compact and repair
the database and then back up the database from our server to a workstation.
We have had a problem occur the last few months. The software people think
it's a problem with our server but I wonder if it may be something with
Access, possibly as a result of one of the updates. Our version is 2003, SP
2.

When we try to compact and repair the database, we get an error and the
system changes the file name to dbl. I have to rename it in order to run the
program. The error message we get begins "Microsoft Office Access can't
delete [server:\foldername\filename.mdb] after compacting it. The compacted
database has been named [server:\foldername\dbl.mdb"

This occurs randomly but seems to be happening more often and we can't seem
to find a pattern. Any ideas?

 

[Guest]

I went back and checked and it is compacting over the network. I'm checking
with the software people now. Again, thank you.

Are you compacting the database over the network? If so, you might consider
copying the file over to your local computer and then compacting from there.
Unless you have a really reliable network or a really small data file,
there's a lot of ways compacting over a network can cause problems (e.g. data
corruption that doesn't cause Access to throw an error message).

Our fiscal software is written in Access. Every day we compact and repair
the database and then back up the database from our server to a workstation.
We have had a problem occur the last few months. The software people think
it's a problem with our server but I wonder if it may be something with
Access, possibly as a result of one of the updates. Our version is 2003, SP
2.

When we try to compact and repair the database, we get an error and the
system changes the file name to dbl. I have to rename it in order to run the
program. The error message we get begins "Microsoft Office Access can't
delete [server:\foldername\filename.mdb] after compacting it. The compacted
database has been named [server:\foldername\dbl.mdb"

This occurs randomly but seems to be happening more often and we can't seem
to find a pattern. Any ideas?

 

[Tony Toews]

Are you compacting the database over the network? If so, you might consider
copying the file over to your local computer and then compacting from there.
Unless you have a really reliable network or a really small data file,
there's a lot of ways compacting over a network can cause problems (e.g. data
corruption that doesn't cause Access to throw an error message).

FWIW I routinely compacted a 200 - 300 mb database over the network
without any troubles. Every month or so for years.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm