This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Microsoft Dynamics GP 2013 added a long awaited feature, the ability to change the printer selection for a report after it has printed to the screen output.
Named Printers
Using Named Printers with Terminal Server revisited
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
This is an update to the original Using Named Printers with Terminal Server post from August 2008.
Named Printers application default printer selections not “sticking”
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
In the past, I have had some cases where users have reported that the Microsoft Dynamics GP application default printer as set by Named Printers keeps getting changed back to the Windows Default printer. The cause of this issue was never really identified…. until now. A current case with a similar issue finally helped explain what was happening.
Troubleshooting Named Printers Issues
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
I am working on a Named Printers issue at the moment and thought it would be a good opportunity to put some standard troubleshooting steps on the blog.
Quick history: I originally developed Named Printers back on version 3.0 when I worked for the selling ISV partner, Sequel Technology, and later sold the module to Great Plains Software for version 5.5 and it became part of the core Dynamics.dic code for 6.0.
Using the Support Debugging Tool to create temporary fixes
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
The Support Debugging Tool for Microsoft Dynamics GP has the facility to create non-logging triggers. This are Automatic Debugger Mode triggers that do not automatically start and stop the Dexterity and SQL logging.
Hybrid – Adding Named Printers control to Reports using VBA
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Named Printers is a module to allow controlling of the printer and settings used when printing reports. It was originally developed for v3.00 by me while I was working for Sequel Technology (that’s why the tables and calls are prefixed with ST). Later it was purchased by Great Plains for v5.50 and included in core code (Dynamics.dic) for v6.00 onwards.
Hybrid – Purchasing Terms & Conditions Example
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
This example shows how you can call a Dexterity report from Visual Basic for Applications (VBA). The report can be either a built in report or a custom report. If a built in report is used security will define whether the original, modified, alternate or modified alternate version will be printed.
Using Named Printers with Terminal Server
This is a reposting of an article I originally wrote on my Developing for Dynamics GP blog.
Some of you might know that I was the original developer of Named Printers. I was working with the West Australian partner Sequel Technology at the time. It was created back in version 3.0 as a customisation for a distribution client who wanted to be able to print SOP picking tickets to the warehouse while printing the SOP invoices to the accounting department’s printer.
