Just by chance.. you said that this was first being attempted to be done on the ??same printer?? that was on a network.
If so then could the driver have not gotten uninstalled (when it was first setup to the network) and the new driver for it that should have it setup to the local LPT1 gotten installed and it have some wires crossed somewhere?
I hate to say this, but we have a time or two where we have gotten really brave/crazy and removed all printers, then deleted any reference in c:\program files for printers.. and then after backup of it went into the registry and deleted all places where we found references to printing.. Like for HP prrinters we searched first for the model# 1215 or so.. and then went through all references for HP and deleted most of them that we thought was associated with Printing..
This has worked more than once, but I reccomend this as a VERY last resort.
I think HP and some other manufacturers provide registry cleanup software for some models and maybe generic cleanup utilties...
When you say: > If I do a prnsetup and choose the local > printer, then nothing comes out.
Do you mean just after this large routine you have done has run, or just trying this connected to db at any time?
Jim Limburg
[EMAIL PROTECTED] wrote:
Albert:
Was this in DOS or in Windows? The reason I ask is that I thought that the LPT1 part would be ignored in Windows, that it goes to the current printer no matter what you say.
OUTPUT tempfile.txt SET LINES 0 LIST <tablename> SET LINES 20 OUTPUT LPT1 TYPE tempfile.txt NEWPAGE OUTPUT SCREEN
Jim:
Well, yes and no. If I do a prnsetup and choose the local printer, then nothing comes out. If I do a prnsetup and choose a remote network printer, then it comes out. And remember that if I choose the local printer and print an RBase report it does work, just not if I type a file.
>So.. your saying if you do a prnsetup and then >have the user type the commands >output printer >type &vfilename >output screen >This works..
Karen
