Check for SQL triggers on the tables.  I had one upgrade recently where updates to the GL were blocked entirely because of a 3rd party editing the database, adding triggers that were broken on the new SQL server.  (Which has nothing to do with Sage 100).

Check for SQL triggers on the tables.  I had one upgrade recently where updates to the GL were blocked entirely because of a 3rd party editing the database, adding triggers that were broken on the new SQL server.  (Which has nothing to do with Sage 100).

Thanks for that suggestion Kevin. I looked at multiple SO tables, none of which had any triggers. I found that there was some custom programming related to EDI, that was indexing and reviewing the sales order history and history detail tables, I think as a way of avoiding duplicate EDI records. They should be providing an updated installation file, which hopefully will resolve the issue.