Hi

I have made a 'database corruption utility' tool for our customers to use to determine which records in a specific table are corrupted (as happens often with access). My program creates a temporary table in a new database, and copies all data from the source table to the new one. I have included error trapping during the copy table routine, but that does not stop the program from showing the dreaded "___ has encountered a problem and needs to close. We are sorry for the inconvenience." error report dialog box.

It seems that when reading the corrupted record in the table being searched, the error is not trapped by visual basic and it just crashes.

Is there ANY way to trap these kinds of errors???