Yes. I ran that experiment several years ago. If you don't group the
output into a file other print jobs can write through and you wind up with a
total mess. By copying a file into the server print stream you isolate the
report output from other Windows print jobs.
======================================
At 09:25 AM 7/5/2001 -0400, you wrote:
>Bernie :
>
>>>
>.....
> Given that you are using RBase for Windows there are several ways I
>can think of to overcome this problem:
> 1) Create a PAGEMODE report which can be written to a file which
>is
>then copied to the printer.
> 2) Use write statements to mimic the report and write them to a
>file which is then copied to the printer.
> 3) Write the report output to a table, then write the table
>contents to a file and copy the file to the printer.
> All of these methods bypass the Windows print control system and
>also allow for insertion of printer control codes.
><<
>
>Did you experiment what happen if at the same time an other windows
>process prints thru the windows printer's manager ?
>(mixing or not ?),
>
>Do you COPY with RBW COPY command, or with DOS COPY (ZIP command.com /c
>COPY ... ).
>
>J.M. GRATIAS, Logimatique, France
>
>
