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

Corrupt database - 1 step forwards....

P: n/a
aaj
Hi all

I have been given a corrupt access 2000 backend and asked to salvage the
data.(youve gussed it, no backup)

On trying to open it just kicks me out saying its not a valid database
file - so I can't even use the internal compact/repair function

I have tried the usal stuff i.e.
Trying to repair via another access program using dao
DBEngine.RepairDatabase
Opening a new database and importing the old data
microsofts JETCOMP.EXE
plus a few other bits

The only luck I have had is do create a new ODBC connection and use this to
compact the database file. It seems to work and creates a new file

If I try open the new file using Access I get 'Query engine error:
42000:[microsoft][ODBC Microsoft access driver] record(s) cannot be read;no
read permission.'
..
If I then use say crystal to look directly at the ODBC connection I can see
the datatables (so there is still something there), but as soon as I try to
view the data I get the same message.

Is there any way I can get in and some how give read permissions to the
tale, or any other suggestions would be brilliant.

thanks

Andy

Nov 12 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
In Access 97 you can open Access without opening a database then use the
database utilities to repair your database. Make a copy before doing the
repair.

"aaj" <a.*@c.com> wrote in message
news:3f***********************@news.easynet.co.uk. ..
Hi all

I have been given a corrupt access 2000 backend and asked to salvage the
data.(youve gussed it, no backup)

On trying to open it just kicks me out saying its not a valid database
file - so I can't even use the internal compact/repair function

I have tried the usal stuff i.e.
Trying to repair via another access program using dao
DBEngine.RepairDatabase
Opening a new database and importing the old data
microsofts JETCOMP.EXE
plus a few other bits

The only luck I have had is do create a new ODBC connection and use this to compact the database file. It seems to work and creates a new file

If I try open the new file using Access I get 'Query engine error:
42000:[microsoft][ODBC Microsoft access driver] record(s) cannot be read;no read permission.'
.
If I then use say crystal to look directly at the ODBC connection I can see the datatables (so there is still something there), but as soon as I try to view the data I get the same message.

Is there any way I can get in and some how give read permissions to the
tale, or any other suggestions would be brilliant.

thanks

Andy

Nov 12 '05 #2

P: n/a
aaj
sorry,

forgot to mention that I tried this as well (in Access 2002) (but with no
joy)

andy

"paii" <pa**@packairinc.com> wrote in message
news:vn************@corp.supernews.com...
In Access 97 you can open Access without opening a database then use the
database utilities to repair your database. Make a copy before doing the
repair.

"aaj" <a.*@c.com> wrote in message
news:3f***********************@news.easynet.co.uk. ..
Hi all

I have been given a corrupt access 2000 backend and asked to salvage the
data.(youve gussed it, no backup)

On trying to open it just kicks me out saying its not a valid database
file - so I can't even use the internal compact/repair function

I have tried the usal stuff i.e.
Trying to repair via another access program using dao
DBEngine.RepairDatabase
Opening a new database and importing the old data
microsofts JETCOMP.EXE
plus a few other bits

The only luck I have had is do create a new ODBC connection and use this

to
compact the database file. It seems to work and creates a new file

If I try open the new file using Access I get 'Query engine error:
42000:[microsoft][ODBC Microsoft access driver] record(s) cannot be

read;no
read permission.'
.
If I then use say crystal to look directly at the ODBC connection I can

see
the datatables (so there is still something there), but as soon as I try

to
view the data I get the same message.

Is there any way I can get in and some how give read permissions to the
tale, or any other suggestions would be brilliant.

thanks

Andy


Nov 12 '05 #3

P: n/a

On Mon, 29 Sep 2003 14:29:54 +0100, "aaj" <a.*@c.com> wrote in
comp.databases.ms-access:
If I try open the new file using Access I get 'Query engine error:
42000:[microsoft][ODBC Microsoft access driver] record(s) cannot be read;no
read permission.'
That's because the compact that seemed to work actually failed, and
the resulting file is missing key system structures, like, for
instance, the security table. That's why you get the permission
error.
Is there any way I can get in and some how give read permissions to the
tale, or any other suggestions would be brilliant.


That won't help. The compact that failed (without an error) did not
just result in a missing permissions table (which is the error you
got) but also other missing system structures, and probably missing
data tables too. Basically, the compact failed at some point -
presumably while processing one of your tables that had corruption,
and simple then bailed on the compact. The resulting file is
therefore missing any system structures that get written at the end of
the compact process, as well as any of your tables including and
beyond the first problem table encountered. So correcting the
permissions problem on the compacted database would, even if
performed, almost assuredly be a largely incomplete file.

The file you need to work with is the original corrupt file (before
the attempted odbc compact). Sending that file in to a service like
ours (www.pksolutions.com/services.htm) would result in its being
properly recovered.

Peter Miller
__________________________________________________ __________
PK Solutions -- Data Recovery for Microsoft Access/Jet/SQL
Free quotes, Guaranteed lowest prices and best results
www.pksolutions.com 1.800.987.7716 1.619.839.3900
Nov 12 '05 #4

P: n/a
aaj
Thanks for the extra info Peter, I'll have a word with the guy whose
database it is,
Andy

"Peter Miller" <pm*****@pksolutions.com> wrote in message
news:jm********************************@4ax.com...

On Mon, 29 Sep 2003 14:29:54 +0100, "aaj" <a.*@c.com> wrote in
comp.databases.ms-access:
If I try open the new file using Access I get 'Query engine error:
42000:[microsoft][ODBC Microsoft access driver] record(s) cannot be read;noread permission.'


That's because the compact that seemed to work actually failed, and
the resulting file is missing key system structures, like, for
instance, the security table. That's why you get the permission
error.
Is there any way I can get in and some how give read permissions to the
tale, or any other suggestions would be brilliant.


That won't help. The compact that failed (without an error) did not
just result in a missing permissions table (which is the error you
got) but also other missing system structures, and probably missing
data tables too. Basically, the compact failed at some point -
presumably while processing one of your tables that had corruption,
and simple then bailed on the compact. The resulting file is
therefore missing any system structures that get written at the end of
the compact process, as well as any of your tables including and
beyond the first problem table encountered. So correcting the
permissions problem on the compacted database would, even if
performed, almost assuredly be a largely incomplete file.

The file you need to work with is the original corrupt file (before
the attempted odbc compact). Sending that file in to a service like
ours (www.pksolutions.com/services.htm) would result in its being
properly recovered.

Peter Miller
__________________________________________________ __________
PK Solutions -- Data Recovery for Microsoft Access/Jet/SQL
Free quotes, Guaranteed lowest prices and best results
www.pksolutions.com 1.800.987.7716 1.619.839.3900

Nov 12 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.