|
|
|||||||||
|
|||||||||
|
|||||||||
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
Free Web 2.0 Code Generator! Generate data entry and reporting .NET Web apps in minutes. Quickly create visually stunning, feature-rich apps that are easy to customize and ready to deploy. Download Now!
|
|
#1
|
|||
|
|||
|
Access Database Recovery
I am getting the error 'Record(s) cannot be read; no read permission on 'MSysAccessObjects' and the database will not open.
I have tried MicroSofts JetComp.exe with no luck, I have seen there is various programs avaliable that will fix the file (I have tried the demo and it restores, but cannot save the file in demo version). Does anyone know of any free software or code that will recover access files or am I going to have to put my hand in my pocket!?! |
|
#2
|
|||
|
|||
|
The trick I use sometimes when things corrupt and can't be easily repaired is just make a new database and import everything from the corrupted one. This almost always* works for me, hopefully it will for you. You'd still need to change certain properties, etc, but at least you should be able to recover all your tables, queries, modules, reports and forms.
Good luck. * Almost always = actually it has never failed me, but I don't want to make promises :-) |
|
#3
|
|||
|
|||
|
I've tried that one, and just get the same error message when I try and import...
|
|
#4
|
|||
|
|||
|
Have you or someone else working with this database recently been doing things with Workgroup Information Files (System Databases)? That's normally what this error means. Multiple WIFs have been implemented with a database and the permissions have been messed up.
If that's the case, the best (free) utility I have found for checking and changing permissions in an Access database is Microsoft Access Permissions Explorer. If the MSysAccessObjects table is the only one to get messed up, you will still be able to connect to the database and browse/fix the permissions. This program connects to the database through JET and DAO. Jet doesn't use that table at all and never accesses it, so permissions for it are irrelevant. If the permissions on the other system tables are messed up then you will need to find the right WIF to be able to connect to it. If this problem truely is a result if database corruption and compact/repair has no effect (and it rarely does in these cases) then there's not much hope unless you are willing to spend some money on an Access recovery program/service. |
|
#5
|
|||
|
|||
|
Hi,
I think you can try a utility called Advanced Access Repair to repair your Access MDB file. It works rather well for my corrupt Access MDB files. Its web address is www datanumen com/aar/ Just post to hope my experience will help. Alan |
|
#6
|
||||
|
||||
|
Quote:
Thanks for the info,.. and welcome to the forum. The thread is 5 months old,.. please do not resurrect old threads,... ![]() |
|
#7
|
|||
|
|||
|
Quote:
|
|
#8
|
|||
|
|||
|
Quote:
That fyz has resurrect another old post recommending the same product. I won't be surprised if he owns the product. |
![]() |
| Viewing: ASP Free Forums > Database > Microsoft Access Help > Access Database Recovery |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|
|
![]() |
|