Dennis, you are my new hero! I don't know how you knew that MS added
that stinking form feed, but that was what I thought was the
problem. I used a hex viewer and the extra formfeed was there...I
figured I was doing the Rbase report incorrectly. The PRINT command
seems much faster....is there any way to strip the extra final form
feed that the PRINT command creates?
Mike
At 12:06 PM 5/23/2007, you wrote:
He's talking about the windows PRINT command which will print a file to
any network printer. Unfortunately, MS got cute with PRINT and adds a
FF which is dead stupid. If one wants a formfeed they can put it in the
file! Or just print another file that has a formfeed in it.
I had to tweak all my reports after NET USE went dead slow on us and I
switched to PRINT.
Dennis McGrath
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Ron Rose
Sent: Wednesday, May 23, 2007 9:59 AM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: NET USE VS PRINT
I look at it this way. The copy software is sending the file thru a
port---- very fast.
With the print, the database is cranking away building the report and
senting it piece by piece thru the network---- all that stop and go.
RRR
----- Original Message -----
From: "Michael Sinclair" <[EMAIL PROTECTED]>
To: "RBASE-L Mailing List" <[email protected]>
Sent: Monday, May 21, 2007 5:00 PM
Subject: [RBASE-L] - NET USE VS PRINT
> Hi all,
>
> In Rbase for DOS, I have a report to print to a network printer.
> I create the report and print it to a file. Then I want to send the
file
> to the network printer.
>
> The following code works...
> zip net use lpt1 \\servername\print_que_name
> copy filename.txt lpt1
> zip net use lpt1 /delete
>
> The following code gives an extra (unwanted) form feed...
> zip print /d:\\servername\print_que_name filename.txt
>
> Why would there be a difference?
>
> Thanks
>
> Mike
>
>
> !DSPAM:46523612315627787518299!
>
>
