how do you define "bad records:?  you can purge zero quantity records with the utility in Inventory 

Hi BigLouie,

A Customer did an import without Receipt Number and now we cannot access those tiers (638 of them).

They are not 0 quantity tiers.

Export to Excel, Reinit the file, import the good records back in. Only way it can be done for that many.

IM_ItemCost is an audit table holding your inventory value.  Do not purge! 

What do you mean "Customer did an import..."?  VI allowed you to add rows to this table?!?  Never, never, never do this.  Always import to a data entry table and post.

If you have an issue with logically bad data (not technically bad data), use normal transactions (not data utilities) to fix them.  If VI allowed bad data to be inserted, use DFDM to selectively delete the bad rows.  Again: do not purge!

Kevin, notice he said he has 638 rows of bad data.

Kevin, notice he said he has 638 rows of bad data.

I noticed, and have seen worse.  Re-importing this specific table is a very BAD idea (breaks the audit trail of the data: resets DateCreated, UserCreated...).  At this point I assume restoring a full system backup is impossible (which would have been ideal, if noticed immediately).

Charge the customer by the hour for the manual fixes, and it should serve as a good lesson for them to try risky imports in a test company before running Live.

I've had to do what Kevin has suggested on occasion, and it is really the best way to fix what has happened here, if a network backup can't be restored.  And it does not require the users to be completely out of Sage 100 while removing those incorrectly imported data records.