>>That's pretty much what we are doing, although I didn't realize the no header/footer part. We accomplished that by accident. Basically, we used to just send the data straight out the port, but to fix various problems such as multiple people printing to the same printer at the same time, and of course trying to actually hit the printer port under Windows NT, we are just sending it to an alt file, and then pulling the alt file into a temp database and printing a report which just has one field to display each line. We managed to get it working using a generic text only driver.
>>
>>It isn't very elegant, but it gets the job done!
>>
>>Thanks for the tip,
>>Paul
>
>***************************************************************\
>One thing I don't understand,
>Why are you sending report to file, to be pooled into something,
>and then sent directly to the port ? Why dont you simple
>flush report to printer spooler and let it do it's job?

We are sending the report to a file to minimize recoding. We are talking about literally hundreds of reports that we used to send straight out the port using the ? command. Now that we are using the windows printing systems, most of those reports were just converted to text files which we can then append into simple databases and then send out using generic report forms for different pitch sizes. Based on the way our code was created, we only had to make a couple of coding changes to make all of those reports work as opposed to rewriting every report. The only hangup was with the receipts, and this seems to take care of it.

I know it isn't the best solution, but it was fast and it works.