Charles, thank you. I created the generic text-to-file printer and the print job went to the Windows spooler but never prompted for Output Name, for example d:\temp\prh, as did the Windows test print job which generated the job to file fine. So the job never made it out of the Windows spooler on this test.
I will verify this on a different machine printing from UniVerse to a Windows defined FILE to see if this is machine specific. Paul H. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, August 09, 2005 4:26 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] Remote printing in UniVerse release 10.1.3 I suggest that you set up a generic Text-to-file 'printer' and route to it. If it doesn't get to the file, you know the printer itself isn't the problem. If the generic text file does generate, I'd look to see if so step is adding control chars which are affecting the printer. -- Charles Barouch [EMAIL PROTECTED] - Consulting [EMAIL PROTECTED] - ETL/Migration/Integration (718) 762-3884x1 Paul Hamrick wrote: > Can you lead me to some possible causes for the UniVerse job to not > reach the printer? ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
