Sage 100

I upgraded a client on Sage 100 Std 2013 to PU9 and loaded the 2015 IRD. Now when anyone opens SO Data Entry or SO Invoice, and enters a new or existing SO or Invoice, they get an error 88. All other modules seem to be ok. If I switch to a different company, I get the same error. Client does not use any form of credit card processing or CRM. Sage Support seemed to think it might have something to do with a 3rd party app showing up in the MAS90\links folder, although the 3rd party app is actually the GL sync for the last payroll service Sage no longer supports. That app imports a GL entry from the Payroll Service. I have run the customizer utilities, reinstalled WS setup, and run the WS Std Update. Waiting for Sage to research. Does anyone have any ideas where I might look next?

Is the ""Calc Ship Date"" a UDF? Part of a script?

Have you tried renaming the links folder and running SO entry to at least isolate those files as the source of the problem?

Any user-defined scripts? Error 88 usually means a typo or missing variable. Does the error happen on a non-customized version of Sales Order Entry?

The Calc Ship Date is a link to a script that calculates the ShipExpireDate based on order date and a UDF storing the lead time in days.

I have not tried renaming the links folder. I will try that after the client has left for the day.

I have tried creating a new form. No scripts or custom changes of any kind. Still get same error.

Okay, I was able to track this down for you. The line number in the SO_COMMONPAYMENT_BUS program is attempting to find another variable called ImportTest. This looks like it's new for PU9. It took me awhile but I was able to find it in the AR_CREDITCARD.PVC. Note: Even though your client doesn't use CC, sales order and invoice entry does loads these programs automatically. When you get onto your client's system, check the date of the AR_CREDITCARD.PVC program. I was able to get it to not error using one that is date 1/7/14. I'm pretty sure it's a program incompatibility issue.

Well, Per Justin's suggestion, I tried renaming the Links folder and the problem did go away. The file date of AR_CreditCard.pvc when the error occurs is 1/7/2014 11:27 AM. The Pre-update (working copy) of AR_CreditCard.pvc file is dated 9/3/13. That is with version 5.00.4.0.

Marcos, since Sage is still apparently ""researching"" the issue, do you think it would be beneficial for me to contact them and provide them the file information you have identified, or is there something further that I should try. At the moment, I have the client running on the pre-update backup copy. I also have the post-update error-prone copy available for testing.

Chris, I'm curious. Can you email me both versions of AR_CREDITCARD.PVC? I just want to compare them with what I have. Also, was AR_CREDITCARD.PVC, by chance, one of the files in the Links folder?