David,
Have you tried putting the output to a file first and then printing that?
Look at the properties for the printer and see if there is a form feed option.
Instead of doing writes to the printer, how about creating a temp table w/ a
note column and building a report that runs off of it.
Good Luck,
Troy
>===== Original Message From [EMAIL PROTECTED] =====
>Dear All
>
>I recently completed conversion of a very old R:Base System V application to
the redoubtable glorious R:Base 6.5++. The client is thrilled with the
application. There is just ONE issue to be solved.
>
>In the application, which is a summer day camp program in Maine, printing is
done to an Okidata 370 Turbo dot matrix printer because they need to print
receipts on carbon paper. One of the "reports" generated by the system is
actually created by a series of WRITE commands
>sandwiched between OUTPUT PRINTER and OUTPUT SCREEN.
>
>When I run this report on my system (Windows 95 and an HP LaserJet Series II
printer, hooked up as local printer) it prints the page and does a form feed.
When he runs it on WIndows 98 or Millenium, under a Windows peer to peer
network, with the printer set up as a network
>printer, it prints the page, and does TWO form feeds, wasting a full set of
carbon paper. Doesn't matter which work station he prints from.
>
>When he runs this under the old System V application, in a DOS window under
the same Windows 98 or Millenium to the same printer, it doesn't even do ONE
form feed, which is really what he wants.
>
>Any ideas? Is there a setting somewhere in R:Base, Windows, or Peer to Peer,
or the printer that we can change to give him what he wants?
>
>David Blocker
Troy Sosamon
Denver Co
[EMAIL PROTECTED]
