Update:
This turned out to be a different issue than what I thought.

We have been compiling the EXE without checking the PBD or DLL boxes on the library tabpage in order to compiled the entire application into the EXE. This has worked well for decades.

I noticed, though, that the size of the EXE generated the last time I deployed the code was one third the size of the previous EXE. Not good. The PrintGetPrinter() issue just happened to be the one that was most noticeable when running the EXE.

I compiled the utility with a DLL and the problem went away.


// -------------------------------------------------------

PBv12.1, b7055
Windows 10, 64 bit platform


What runtime DLL is required in PBv12.1 to call the PrintGetPrinter() command?


DETAILS:
We have this utility, on PBL, compiled into an EXE + DLL.
On it there's a command button to "Change Printer".
Here's the list of runtime DLLs that are packaged with the two utility files:

The commnad button has one line of code: 
    OpenWithParm(w_set_default_printer,'ROOT')

This is the OPEN event of the window:


When the PrintGetPrinter() is called ,the app aborts silently - no error msg, no warning, no nothing - it just vanishes. This occurs in the PB IDE and during runtime.


Thank You,

Olan