4D client v16, and v17
MS Windows RDS terminal serving, Server 2008r2, fully patched
4D client, running in MS Windows RDS (terminal server) often has problems detecting the current printer.
We use a 3rd party product called “TS Print” (as in “Terminal Server” print – by TerminalWorks). Often, when 4D client launches it doesn’t get a current printer (about 25% of the time). When I say “it doesn’t get a current printer”, I mean
The Get current printer command returns a null string
GET PRINTABLE MARGIN Returns all zero’s
4D is seeing a list of printers (with the PRINTERS LIST command), but just doesn’t get a current printer.
I’ve tried using the SET CURRENT PRINTER command, but it doesn’t fix the problem. I executeSET CURRENT PRINTER to a printer that is listed in the current printer list, but when I read Get current printer again, I still get a null string
However, if we launch Notepad in the same user session, we are typically able to see the user’s current printer, and print.
If Notepad can get a current printer, and print, why can’t 4D?