Long story shortish...We helped a client with some integration from a nesting program(ProNest) into MAS 90 4.40.0.8 through JobOps. Until we caught the mistake were able to import about a months worth of Parts Usage with a bad date format(MM/DD/YY). That data now resides in the ItemTransactionHistoryFile. The bad dates are causing problems. OK, no big deal, i'll export all the records, re-initialize the file and reimport them. Import job tests fine but when you actually run it, every record fails: Record is not in an editable state. Am I screwed(manually make all the changes in DFDM) or is there a way around this?