If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

My db is sitting on a n/w that's accessed by everyone. It got roasted this morning and now everytime i try to access it, i get 2 kinds of errors. It doesn't even allow me to compact and repair cuz the moment i try to open it, that error msg pops up.

1. The microsoft access database could not find the object 'MSysDb'. Make sure the object exists and that you spell its name and path name correctly.

2. Error 3011: The microsoft jet database could not find the object 'MSysDb'. Make sure the object exists and that you spell its name and path name correctly.

I've tried a lot of free tools, even jetcom.exe but no help. The mdb repair tools available on the net are not free to save the file. Does any one know a cracked version or where i can download a tool to fix the currupt db.

I really really need the db by monday. Any help would be really appreciated.

I might also try creating a new mdb and see if you can import the objects into it. This really sounds like a database corruption issue and since you can't repair the mdb, I would see if you can perhaps import (or export) the objects into another mdb, especially if time is critical.

Also, I'm assuming you tried opening the mdb using the shift key.

Try copying the mdb to a local drive and see if you can do any compacting/repairing on your local drive (I believe it's always better to try and do this kind of stuff from a local drive, and of course, a backup copy.)

As a note, asking for a cracked version of a software is not a good idea on this site.

I might also try creating a new mdb and see if you can import the objects into it. This really sounds like a database corruption issue and since you can't repair the mdb, I would see if you can perhaps import (or export) the objects into another mdb, especially if time is critical.

Also, I'm assuming you tried opening the mdb using the shift key.

Try copying the mdb to a local drive and see if you can do any compacting/repairing on your local drive (I believe it's always better to try and do this kind of stuff from a local drive, and of course, a backup copy.)

As a note, asking for a cracked version of a software is not a good idea on this site.

Your mdb

Here's your mdb after I ran it through a few utilities I had. It doesn't recover the Forms, Queries, Reports, and Modules but your tables are all there. I hope you have a backup for the other objects and hope this helps - best I could do. As a note, you have a lot of tables without an autonumber (or primary key designated) field. I would highly encourage you to create autonumber fields for ALL your tables and perhaps set some primary key fields. Autonumber type fields (in my opinion), helps maintain a good clean table which helps prevents some database table corruption problems. Defining Primary Key fields will also help in maintaining good recordsets (but perhaps the utilities I used removed these.)

Thanks a million stormy. I do have tables with autonumber, just couldn't be recovered. With this zip, i lost all the data that was there.
Can you let me know how did you manage to recover. It'll be very helpful if something like that happens in the nearby future.

Thanks once again.

Originally Posted by pkstormy

Here's your mdb after I ran it through a few utilities I had. It doesn't recover the Forms, Queries, Reports, and Modules but your tables are all there. I hope you have a backup for the other objects and hope this helps - best I could do. As a note, you have a lot of tables without an autonumber (or primary key designated) field. I would highly encourage you to create autonumber fields for ALL your tables and perhaps set some primary key fields. Autonumber type fields (in my opinion), helps maintain a good clean table which helps prevents some database table corruption problems. Defining Primary Key fields will also help in maintaining good recordsets (but perhaps the utilities I used removed these.)

Yes - that can be a problem with a corrupt mdb and a msysdb error (although I thought I saw your data in the tables.) As StarTrekker mentioned, your best option is to restore from a backup with this kind of corruption. Hopefully you have a backup somewhere.

Something I might recommend if you aren't already doing this:
I personally use SQL Server which has a great backup system for the tables (Point-in-Time restores from SQL Server are unbeatable!! I'll set it so it backs up the tables every hour or every 4 hours.)

If SQL Server isn't an option (even though SQL Server Express is free), I'd recommend (if you haven't already), that you split the mdb/mde and again, have the mdb with the tables on a network drive which is backed up nightly (so the most you'll lose is 1 days worth of data if there is a corruption problem.)

For the mdb source code, I keep that safely hidden on my drive (and have the network guys backup my mdb folder). I prefer doing any mdb work off of my local drive to remove any network hiccups out of the picture for any problems. I always do a quick copy->paste before doing any coding work (I may have 10-20 copies of the mdb at the end of the day and then put these in folders labeled with the date.) After a week or so, I'll go through and remove older backup folders. And then I make an mde file which I throw out on the network drive for the users.

I can't help you much more on the mdb you uploaded. If I had more time, I could probably try a few other things (stabbing in the dark) but the msysdb error is a nasty one to try and overcome and fix. I'll usely go to my backups with this kind of error since it can be time-consuming trying out different ways to recover the mdb and may not even get results (and honestly, I'd only go to that extreme for my own mdb - I did this rather quickly on your mdb.) Admittingly though, I've rarely ever gotten this type of error since I do tend to compact/repair on a daily basis as well. You can try one of the services which may help you restore the mdb but you may not get much more than just the tables restored (but you never know.) It's not terribly expensive to have them give it a shot (I think around $100-$200 but don't quote me on that.)