Nothing on servers ever just stops working for no reason.  Windows updates, anti-virus updates or some other program is installed. Something changed somewhere.  Figuring that out can be a near impossible task sometimes and that sucks.

Maybe try re-running a workstation install.  I customize screens using VB6 and when there are printing issues the usual fix was to copy one of the a4w files relating to crystal into the same folder as the .exe.  Crystal is notoriously terrible at figuring out pathing. 

You could also try turning on REPCMD in the registry to see if Sage gets part of the way to working with the engine before it fails.

Oh I know, something happened but hosting company said they did nothing. Sage is installed on C: drive of RDS server

Strange that Crystal Viewer can print redirected, thanks for suggestions I will try them

Brand new server + brand new Sage 300 2019 install has the problem

Just hoping this is not another Excel VBA update mess or VM machine problem by hosting company; at least customer can print to Preview and then out so custom OE and PO windows can work.

Thanks much

here is more info.

1.   Standard screens can print to a remote printer

2.   Macros can print to a remote printer

3.   Sage screens under the control of a macro cannot print to a remote printer; even though they used to all the time; and they do at all sites we work with.

4.   A button on the form to to print with the usual

Dim rpt As AccpacCOMAPI.AccpacReport
Dim rptPrintSetup As AccpacCOMAPI.AccpacPrintSetup

programming works also.

A macro of just userform1.show and a drop on of the ocx fails to print direct to remote printer. Both OE and PO.

I am going to have to blame the hosting company pretty soon.

Put a copy of ..\RUNTIME\a4wcrinterop.dll in your macro's folder.

thanks for suggestion - no joy

my AVB only has userform1.show in Mainsub and a drop on of the ocx.

this started without changes from me; so I think hosting guys did something to port accessing.

Thanks