Sage 100

Let me ask you a really basic basic question. Is the programming logic to test for a valid printer really so complex that Sage cannot update their Sage 100 product to guard against what appears to be a programming 101 type error? A Printer Name specified in a report setting record for the form code or report is not available or not accessible from the workstation for some reason. For example, the printer driver may have been uninstalled from this workstation, or another user at another workstation may have saved the report with a selected printer that is not available for the user on the current workstation. Clear the PrinterName field in Sy_ReportSetting.m4t for the affected report and company. Determine the company key in Sy_Company.m4t as follows: (Note: This step is may not be necessary if only one company code exists.) Select Modules, Library Master, Utilities, Data File Display and Maintenance (DFDM). Select the ""Sy_Company.m4t"" data file in ""..\Mas90\Mas_System"". Click the Key lookup button, and select the record for the affected company code. Note the Company Key (for example: ""0000000003"") Clear the PrinterName field in Sy_ReportSetting.m4t for the affected report and company as follows: Select Modules, Library Master, Utilities, Data File Display and Maintenance (DFDM). Select the ""Sy_ReportSetting.m4t"" data file in ""..\Mas90\Mas_System"". Click the Key lookup button and select a record that matches the Module Code (such as ""S/O"" or ""A/P"", the Company Key (such as ""0000000003""), and Report ID (such as ""SO_INVOICEPRINTING_UI""). (Note: The last value in the key is the Report Setting. Select STANDARD first.) Click the Edit button. Select the PrinterName$ field from the Field Number list. Delete any value in the Change field and click OK. Delete the Printer Name value for each Report Setting record that exists, where they share the same Module Code, Company Key, and Report ID. Close out of Data File Display and Maintenance again. Try accessing the printing menu task again.

You would think they could just add a simple if/then statement. If printer does not exist, then clear it. I have wondered this myself.

Some days I think Sage's secret mission statement is to convince all of us we should go back to ledger paper...

Does Sage have programmers on staff?

I've had to debug through Sage's printing routines a few times and it has been no fun. There are layers and layers of programs before it actually reads the SY_REPORTSETTING.M4T file. I've found that some of the simplest tasks like this, Sage goes through hoops to get to the end result. I feel the pain.

@MarcosDeLuna - could be why Sage seems to be perpetually advertising for high level tech people. Nobody wants to deal with their legacy providex code -- which probably should have been migrated to another language 15 years ago.

I thought it was migrated to another language 15 years ago - Providex...............

Been there done that (too many times to count) A real PITA for sure. The list of inane procedures just keeps getting longer and longer. One would think it would be getting shorter or is that to much to ask! SHEESH!

This keeps recurring and in each case DEFERRED is the printer name. Of course nobody in the organization is selecting this printer ever.

Wayne, had this happen a few weeks ago, the only new variable was a Windows 8.1 workstation added to their network. They were printing through to a Windows 2003 server with a shared parallel port HP LJ4000 printer (check). They could print out notepad and word to the older printer but MAS90 kept tripping the form to deferred if they used the old printer (I have no idea why?) I did the Sage fix and had them move the check printing to a networked LaserJet with valid print drivers for Windows 8.1 and it stopped happening. Don't know about your situation but this is what fixed it for me.

Thanks Jim - good info. I'm going to check with the user on this.

@WayneSchulz I have seen where DEFERRED is the only printer MAS can see and becomes the default after a failed attempt at printing (maybe the ""MAS has stopped responding... error?) I agree with @JimSteele as well as making sure the printers names are the same and consistent on ALL workstations.

Thanks Greg -- something is occurring which puts the DEFERRED printer in as the last printer used. This then on version 4.3 (may be fixed on later versions) causes instant MAS HAS STOPPED WORKING as soon as someone tries going in and printing that form. The issue is figuring out what is causing it. I could recommend an upgrade though I'm always hesitant that the user pays for an upgrade and what if the error keeps occurring?

I thought seeing only a deferred printer meant that you lost the network connection .....

I am having the same issue at 2 different clients 4.50 + 2013 with a local printer and not all the time The printer is connected via ""Virtual USB port

Wayne, my test was to create a new out of the box form in a Test and Play company and then print it to a printer that I know works from a workstation that wasn't the person reporting the error. Then go to the suspect workstation/person getting the ""MAS90 has stopped"" error and have them log into the Test and Play company and try to print the new form to the printer that works. If they print with no error, have them print the same form to the printer they normally select (in my situation it was an old HP LJ4000). In my case, it blew up every time they used the old printer.

@JimSteele I don't think it is the form it definitely is the printer. I would like to know if the workstation that are having this issue are local printers ?