How certain is a repair?

[John]

Tonight I had a corrupt database which Access was able to repair after I
made my backup. The database seems to be working well again. How certain can
I be that the database is repaired well and doesn't have any hidden errors
still inside. Should I take some other precautions? Should I rebuild the app
beforehand by importing the tables, reports etc in another databse?
Thanks for any advice.
john

[Allen Browne]

The database is probably okay.

Look in the list of tables for any new tables. If you see a name such as
Microsoft Repair Error, read the table to see what it says. You may find
that a bad record was deleted, or an index was dropped. Check the
Relationships diagram (Tools menu) to ensure each table's primary key is in
place and all relationships still exist.

Importing everything into a new app, while not essential, does force Access
to read all the objects from the database. So if there was a problem with
reading an object, it would show up by doing that. Before you do, I suggest
you decompile the app, and ensure that Name AutoCorrect is turned off in the
new app before importing. Then eliminate all references you don't need, and
check that it compiles.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"John" <[e-mail] in message news:er*********@textnews.wanadoo.nl...

Tonight I had a corrupt database which Access was able to repair after I
made my backup. The database seems to be working well again. How certain
can I be that the database is repaired well and doesn't have any hidden
errors still inside. Should I take some other precautions? Should I
rebuild the app beforehand by importing the tables, reports etc in another
databse?
Thanks for any advice.
john

[David W. Fenton]

"Allen Browne" <Al*********@SeeSig.Invalidwrote in
news:45**********************@per-qv1-newsreader-01.iinet.net.au:

Importing everything into a new app, while not essential, does
force Access to read all the objects from the database. So if
there was a problem with reading an object, it would show up by
doing that. Before you do, I suggest you decompile the app, and
ensure that Name AutoCorrect is turned off in the new app before
importing. Then eliminate all references you don't need, and check
that it compiles.

A decompile is only relevant if it's a front-end. Back ends, with
tables only, don't usually have any code in them to be decompiled.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[John]

Thanks Allen,
No new tables appeared and no links disappeared, so I'm not going into the
hassle of importing into a new database. Thanks for the info.
john

"Allen Browne" <Al*********@SeeSig.Invalidschreef in bericht
news:45**********************@per-qv1-newsreader-01.iinet.net.au...

The database is probably okay.

Look in the list of tables for any new tables. If you see a name such as
Microsoft Repair Error, read the table to see what it says. You may find
that a bad record was deleted, or an index was dropped. Check the
Relationships diagram (Tools menu) to ensure each table's primary key is
in place and all relationships still exist.

Importing everything into a new app, while not essential, does force
Access to read all the objects from the database. So if there was a
problem with reading an object, it would show up by doing that. Before you
do, I suggest you decompile the app, and ensure that Name AutoCorrect is
turned off in the new app before importing. Then eliminate all references
you don't need, and check that it compiles.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"John" <[e-mail] in message
news:er*********@textnews.wanadoo.nl...

>Tonight I had a corrupt database which Access was able to repair after I
made my backup. The database seems to be working well again. How certain
can I be that the database is repaired well and doesn't have any hidden
errors still inside. Should I take some other precautions? Should I
rebuild the app beforehand by importing the tables, reports etc in
another databse?
Thanks for any advice.
john