Sage 100

Have a MAS200 4.50.7 where Crystal Form Codes in a print screen is only showing STANDARD, if user clicks lookup there is nothing there to select except the STANDARD. The form directory and crystal files are physically present under the MAS_XXX. If we hand key a known form code it will print / preview. I have looked at the SY_LastFormUsed.m4t, SY_ReportOption.m4t which both look okay as far as I can tell (they have records for SO Invoices). The SY_ReportSetting.m4t only has AP, AR, and BR records and nothing else - could this table be the problem? Appreciate any input, large Sage install entity and large number users affected. @Sage100Routine @Sage100Routine @AlnoorCassim

any enhancements? I'm having this issue right now with the barcode module (written by scanco). When i launch Barcode > Reports > PO Receipt Label Printing, i can see all my form codes, if i launch PO Receipt Label Printing as part of the update process when answering yes to the prompt to print barcode receipt labels, i can only see standard. This is because SY_ReportOption is missing records for the PO module but has them under the BC module. SY_ReportSetting may be involved as well but i definitely have a problem in SY_ReportOption. haven't fixed it yet as i'm still in the process of documenting steps to replicate so i can send to scanco. But i should be able to just dfdm the B/C record i'm after and change it to P/O and when prompted to delete the old key, click no. Make a backup too just in case you accidentally do something else.

Hi Bruce try the old trick of typing in your specific form code (overwriting STANDARD) at the time of Invoice Printing then doing a successful Print or Preview of an invoice. Then open S/O Invoice Printing again and hopefully now the ""new"" form code is retained.

For the record, i tried that too, and although the description is populated, printing/previewing, closing , and attempting to print during the update again, yields the same results, form code not visible in the lookup but can be typed in.

We do not have any mods. I have a test upgrade for same client and just confirmed my v450 test copy and v2018 test both have records the v450 is missng in SY_ReportSetting, 1571 records vs 348. I see a restore from backup in my future for MAS_System.

As a test, on your v450 test copy you could reinstall S/O module + SP7 to see if Sy_ReportSetting, Sy_ReportOption, and Sy_ReportManagerMaster will be repopulated with the missing S/O records. That is assuming the 4.x installer allows you to specify location of test \mas90 folder.