Quote:
Originally Posted by mmccarthy
Assuming you are using a backend/frontend application. Give all users their own copy of the frontend application. This way there is only one user of each frontend. As long as they all point to the same backend data it shouldn't be a problem.
We are actually using a front end/back end. If you remove the compact on close from the front end, no problem (not necessary anyway). The backend is still used to reload data and unless you remove the compact on close, it appears that the compact and repair never completes. It creates a db1.mdb, moves everything in, but never renames and deletes the original. So you end up with db1.mdb, db2.mdb etc. And a non compacted database.
The short term solution is of course, to remove the automatic compact on close, do it manually on the hard drive and copy to the network. I am curious as to why this is only a problem on the network. And I am hoping for a more long term solution that does not rely on the person reloading to move the database down and compact it manually.
I am finding more of this issue on other forums, at this point I have narrowed the suspects down to one. The SP3 service pack. I guess we will have to wait for Microsoft to notice the complaints and come up with a fix.
