Corrupted database much slower now--ideas on repairing?

[MarkGibson]

When I was last at my client's office, working on their multi-user Access 2000 database (shared across an ethernet network of 5 users, with a 2Meg backend on the server and a 7Meg front-end on each machine), the database got slower and slower and finally crashed at the end of the day; the machine I was on has Access 2002, and it was unable to compress and repair the database, even after several tries, and even when I quit and re-opened Access 2002. Finally I was able to copy it to my laptop, which has Access 2000, and repair it. It worked, and I was able to continue development on my machine.

When I came back to the client today and installed the latest version, it was very slow, about half the speed that it was when I left. This week's development work has not, as far as I know, altered any of the file structures or the data access mechanisms. I presume that there is corruption hidden in the background.

This has happened before, usually with crashes under Access 2000; sometimes I have had to redo the last few hours of work. Each time the db seems slower.

What can you suggest as a way to clean things up and start afresh? Of course I have run Tools: Utilities: Compact and Repair many times, under both 2000 and 2002.

Thanks for your help!

 

[aexley]

How about importing each table in the back end into a new clean database, renaming your original and using the copy?

I have had some problems with crashes (mainly due to my inexperience with VB) and have had some success with this.

Hope it helps.

 

[MarkGibson]

Thanks; I will try this. I had been presuming that the problems were likely in my front end, and trying to figure out how to clean it up. I won't really know whether it worked until early next week when I am on the client's network again.

Mark

 

[MarkGibson]

On second thought, I don't think it can be the back end, because I gave a user an older version of the front end to use, and she got faster results. What I will try is relinking the tables (between the front- and the back-ends), to see if that helps. I have also added one table to the front end (all the rest are in the back end); I wonder if this could confuse Access?

Mark

 

[aexley]

Just a thought and I'm sure you've tried it, but how about running 'Analyze - Performance'? It could point out issues with your code or forms that might have been missed.

Hope it helps.

 

[MarkGibson]

I have never tried Analyze before; I will try it. In the meantime, I have found two Microsoft documents that were of some help:
1) How to Troubleshoot/Repair a Damaged Jet 4.0 Database (Knowledgebase Article Q209137;

http://support.microsoft.com/suppor...ase&rnk=4&src=DHCS_MSPSS_gn_SRCH&SPR=ACC2000)

2) Access 2000 Quits When you Add Data Through a Query after you upgrade to Jet 4.0 Service Pack 5 (a new version of Jet40.dll for those having problems; Knowledgebase Article Q304084;

http://support.microsoft.com/support/kb/articles/Q304/0/84.ASP?LN=EN-CA&SD=gn&FR=0)

3) There was also talk on some page about professional database repair services; I have not been forced to explore this yet, thankfully.
Have a great day!