I'm having odd results from Windows API-based printing.
On both Windows 7 and 8.1, I'm using the standard "sequence":-
StartDocPrinter
StartPagePrinter
WritePrinter
EndPagePrinter
EndDocPrinter.
Regardless of whether I get the printer information from EnumPrinters or ConnectToPrinterDlg, it prints correctly on directly-accessed network-connected printers, but if I send the job via the spooler on the server the job apparently queues (it shows the job as "spooling") but then nothing happens and the job disappears without printing. Have I missed calling something to release the job to the spooler?
(edited to add) If I use notepad/wordpad/whatever they work perfectly with either the direct-connection or via the server, so the error must be mine somewhere.
Any suggestions gratefully accepted.