How can I fix broken Access database

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

My Office Access 2003 SP2 got corrupted and upon openning shows the message:
The Microsoft jet database engine could not find the object 'MSysDB'. Make
sure the object exists and you spell its name and the path name correctly.
I've tried to use Compact and Repair utility but it got the same message
with openning the corrupted file.
I also tried to import to empty database all of the object but with the same
message and result.
Can anybody help me with this?
Thanks,
Joseph
 
Hi, Joseph.
Can anybody help me with this?
Click to expand...

Restore from last night's backup. You do have a backup, don't you?

Next time you run into a corruption problem, make a copy of the file and
work on the copy. Compact/repair the copy or use JetComp on the copy.
Sometimes JetComp can repair a database when compact/repair can't, because
JetComp doesn't first open the database file like compact/repair does.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.
 
Thanks.
Yes I did restore from yesterday's backup but users lost data they entered
today and I am looking for the way to help them. I just tried the JetComp
utility but it did not help either.
Thanks again.
 
Hi, Joseph.
Yes I did restore from yesterday's backup but users lost data they entered
today and I am looking for the way to help them.
Click to expand...

Microsoft Access data recovery services are expensive. If your organization
can't afford to lose data that was input since the last backup, then the
data should be migrated to a client/server database such as Oracle or SQL
Server, which are much more robust and can restore recent transactions from
the transaction log whenever something goes wrong.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.
 
your organization can't afford to lose data then the
data should be migrated to a client/server database such as Oracle or
SQL
Server, which are much more robust and can restore recent transactions
from
the transaction log whenever something goes wrong.
 
A said:
your organization can't afford to lose data then the
data should be migrated to a client/server database such as Oracle or
SQL
Server, which are much more robust and can restore recent transactions
from
the transaction log whenever something goes wrong.
Click to expand...

Agreed.

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
 
Microsoft Access data recovery services are expensive.
Click to expand...

Peter Miller at pksolutions.com is *not* expensive. If the data is
worth anything at all, it's worth a couple hundred bucks to recover!
 
Hi, David.
If the data is
worth anything at all, it's worth a couple hundred bucks to recover!
Click to expand...

Very true! I was "speaking" relatively. A couple hundred bucks compared to
the cost of the time taken to make a backup and restore from the backup is
far more expensive than I would care to pay.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.
 
Hi, David.


Very true! I was "speaking" relatively. A couple hundred bucks
compared to the cost of the time taken to make a backup and
restore from the backup is far more expensive than I would care to
pay.
Click to expand...

But did he not say he had a backup? And the problem was the lost
data that the users had entered between the backup and the
corruption? The cost of re-entering the data may be much more than
the recovery cost.
 
Hi, David.
But did he not say he had a backup?
Click to expand...

Yes. He's fortunate to have a backup.
The cost of re-entering the data may be much more than
the recovery cost.
Click to expand...

If that's the case, then the data needs to be stored in a client/server
database, not a file-based database that has no built-in recovery method.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.
 
the time necessary to move to SQL Server is trivial, at best

performance gains are worth it; every single scenario
 
f u kid

I was emphasizing what he said.


if your organization can't afford to lose data then the data should
be migrated to a client/server database such as Oracle or SQL Server,
which are much more robust and can restore recent transactions from
the transaction log whenever something goes wrong.
 
Back
Top