By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
464,773 Members | 1,226 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 464,773 IT Pros & Developers. It's quick & easy.

Problem in Compact and Repair datatabse

P: 2
Hi all,

I tried compacting and repairing my database but it took longer time so i closed the database. Then i found one table named as MySysCompactError and i am totally confused now as in that there almost 6 errors it is showing.

Also i am getting an error as "Jet Database Engine could not found the search results" Please helppppp
May 30 '07 #1
Share this Question
Share on Google+
2 Replies

puppydogbuddy
Expert 100+
P: 1,923
Hi all,

I tried compacting and repairing my database but it took longer time so i closed the database. Then i found one table named as MySysCompactError and i am totally confused now as in that there almost 6 errors it is showing.

Also i am getting an error as "Jet Database Engine could not found the search results" Please helppppp
Your mdb is showing signs of corruption. As a first step, try the jet compact and repair using this free tool.
Database Mechanic
If that doesn't help, try the tool's rebuild utility. If that doesn't help, look at the troubleshooting links/tips at the bottom of the site's web page.

If that doesn't help, consider a heavier duty corruption repair tool such as:

Access Fix
May 30 '07 #2

Expert 5K+
P: 8,434
In my (admittedly limited) experience, it is dangerous to interrupt a compact/repair operation in MS Access. I have had a couple of cases where I got impatient and hit Ctrl-C to interrupt. Access immediately stopped the operation, reopened the database and acted as though everything were perfectly normal. Except that I found half of my data had disappeared.

No errors, no indication anything was out of the ordinary. I said "quit" and Access effectively said "Ok, done - what next?".

I find this totally unacceptable. Stuffing up the database is bad enough, but the very least we should expect is for the product to let us know something is wrong.
Sep 14 '07 #3

Post your reply

Sign in to post your reply or Sign up for a free account.