Print job still spooling after FORM command executed

[Boaz Bezborodko]

Kenneth Brody wrote:
> Boaz Bezborodko wrote:
> [...]
>>>>>> According to my reading of the manual FORM should close the spool 
>>>>>> and allow the job to print.  What could stop this from happening?
>>>>> If filePro thinks the output is going to a file, rather than a 
>>>>> pipe, then it will not close the file after each form.  What is 
>>>>> the exact destination filePro has been told to use?
>>>>>
>>>> It is going to a file.  Is there a way to get it to close the file 
>>>> from within the processing table?
>>> If it's going to a file, then what is sending it to the spooler?
>>>
>>> I forget if PRINTER RESET will force the file to be closed in this 
>>> scenario, but you can try it.
>>>
>> OK, I wasn't sending it to the PDF option like I thought.  I had set 
>> it to a different printer using PRINTER NAME, but otherwise doing a 
>> standard print.  Using PRINTER RESET did resolve this problem, though.
>
> Then we're back to the original statement/question:
>
> If it's going to a file rather than a pipe, then filePro won't close 
> the file after each form.  You say it's going to a file, you also say 
> that it's also going to the spooler.  Which is it?
>
> What is the exact destination for the printer name you gave?
>
> In this case, PRINTER RESET works because you used PRINTER NAME to 
> change the destination, sent something there, and now you reset it 
> back to the original printer, thereby closing the 
> temporarily-redirected output.
>
I made a mistake the first time.  It wasn't going to a file, but to a 
printer. 

The command executed was "PRINTER NAME office" where 'office' is the 
FilePro name for a Windows queue (\\fileservername\queuename) that 
services a PrintWizard service.  That service then sends the print job 
to the printer.  When I executed the printout the queue 
(\\fileservername\queuename) would show that it is still spooling until 
I exit IUA.  Now, with PRINTER RESET, it stops spooling right away.