Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

access table crashing

Status
Not open for further replies.

Guest_imported

New member
Jan 1, 1970
0
i have a table that keeps crashing. when i scroll down the table i come to a record that should have text, but instead is filled with alot of different symbols.... once i get to this record the table crashes. i can't even select the record to delete it. is there another way to delete/fix this record??

thanks.
 
There is likely some bad data in that record. I would export all of the other records using a query (or simply copy-paste) to a new table (maybe you can create a copy of the table with no data in it). Then you can delete your original corrupted table.
 
thanks.
that seems to be the problem, but it won't let me export of copy/paste. its still keeps crashing. i even tried saving it as an excel spreadsheet.
 
Do you have a unique identifier in that table (primary key, autonumber etc.)?

If you know which field it is, could you run a delete query to delete that specific record? Or when you make your new table, use "Not " and the unique identifier for the bad record?

Kyle
 
Hi, I have had this problem and this is how I solved it. When you attempt to copy/paste the table to a new table, it copied the rows down to the bad record and then bombed. Open the table and manually copy the records prior to the bad record to the new table. Then skip the bad record/s and finish copying the remaining rows to your new table. It's a pain but less trouble than recreating the whole table.

On my bad records, Access had put #ERR in the bad field. So I can scan for that text in the file when the table bombs. That doesn't always work however.
 
I believe Access stores records in the order in which they're entered which may or may not correspond to the way they're displayed regardless of indexes and primary keys. So scrolling down to a record is no guarantee that you're isolating a discreet set of good records.

Try using DAO to copy the records from the bad table to a new table testing for an error condition on each record copy. If error skip to the next record and see it that gets you what you want.

Uncle Jack
 
Have you tried to Compact and Repair the database? This may remove the bad record for you - it usually works for me.

Basia
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top