Sage 100

Apparently Sage's phones are down. Client tried calling (so they could use one of their free support calls )and Sage is unreachable - all phones are down ??? so they called me LOL Client is on 4.05.40 trying to enter a sales order for a bill item that has options. After selecting the options and clicking OK, the following error appears. Error 26 Variable Type Invalid. Program CI_ItemPrice.pvc. Line 288. Key is the item number. I already rebuilt the item pricing file. The SO screen is customized but I took off the customizations and still had the error. There are NO mods to BM or SO. It is definitely triggered by selecting an option because if I pick the same item and DO NOT select any options, no error occurs. Any thoughts?

Is it one specific option selection? Have you tried different options? It could be something in the bill, option bill or option interaction.

It is looking at the BM_BillOptionHeader - what happens when you go into the bill and open the options? Might debug ? BillOptionCategory$ and see what it returns.

Rebuild the Bill file?

Ok Bill looks fine - debug gave me a blank and going to rebuild once everyone is out of it.

Rebuilt all BM files no errors/no discrepancies. Rebuilt the BM sorts just for fun. Still getting same error.

If you look at the option records for that bill in dfdm you might see a record that looks funny. Sometimes error 26 indicates alpha data in a numeric field.

From Sage's FB page. Doh!

I have seen the issue @RobertaFerguson is talking about, somehow an alpha charachter gets in the option category field on the option bill header and it blows up when you select it.

The two bills that are causing me problems have alphas in the category field! Thanks everyone !!!!

Just an FYI - From @RobertaFerguson and @BernieLehman last post, I ran a Crystal Report and pulled out the category fields and there they were. Sage had no clue and the woman barely spoke English. Some of the phones must be back up and running but not sure from what country. So thanks to All !!!