bradmaunsell
Programmer
This is not a question - I am posting this as a simple "FYI"
This happen to me today and has happened before but I had forgotten how to fix it. So, I made a note and saved for the next time it happens to me. Here it is.
Access 2003 with tables in a separate database and linked to another database containing the application forms, reports, queries, etc.
The problem is one corrupt record in a table. When looking at the open table, all fields (in that bad record) contain "#ERROR". You cannot select the bad record to delete it.
===========================================================
HOW TO GET RID OF ONE NASTY RECORD IN TABLE (#ERROR in all fields)
go to the tables database
RUN THIS (DECOMPLIE)
"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" /Decompile "\\Cambridgesvr\NW Files\PRODUCTION\APPS DATA\InsureProgs_TABLES.mdb"
Open the table and you will see the nasty record now has null in all fields and that record is on top
Select and delete that null record
Compile, and then compact and repair and all is OK again.
Brad
Burlington, VT
This happen to me today and has happened before but I had forgotten how to fix it. So, I made a note and saved for the next time it happens to me. Here it is.
Access 2003 with tables in a separate database and linked to another database containing the application forms, reports, queries, etc.
The problem is one corrupt record in a table. When looking at the open table, all fields (in that bad record) contain "#ERROR". You cannot select the bad record to delete it.
===========================================================
HOW TO GET RID OF ONE NASTY RECORD IN TABLE (#ERROR in all fields)
go to the tables database
RUN THIS (DECOMPLIE)
"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" /Decompile "\\Cambridgesvr\NW Files\PRODUCTION\APPS DATA\InsureProgs_TABLES.mdb"
Open the table and you will see the nasty record now has null in all fields and that record is on top
Select and delete that null record
Compile, and then compact and repair and all is OK again.
Brad
Burlington, VT