I would export the table to Microsoft Access, make a copy of the file, then re-init the file in Sage 100, go into the Access table and delete all the records with no sales order number and then import the table into Sage 100 using ODBC to read the table. This gets around the issue with quotes and commas in descriptions.

I would export the table to Microsoft Access, make a copy of the file, then re-init the file in Sage 100, go into the Access table and delete all the records with no sales order number and then import the table into Sage 100 using ODBC to read the table. This gets around the issue with quotes and commas in descriptions.

I thought about doing that as my first option, but Support felt that without a header record to go with it, and the fact that it is a history table, that VI would not work in this scenario.  If you believe differently, I'm happy to give it a go.

I've never done it, but SO history files are listed as an option in VI.

I'd be super cautious though... because you'd be importing true history, and history lines mirrored for open SO too.  Be sure to test thoroughly in a test company code before trying anything in your Live company code.

I would create a copy company and try it in the copy and if it works do it in the live company. No matter what method you settle on you should do it in a test company first.