Oracle Report Printing to Tally Line Printer Prints Wrong LPI

[mcintysh]

I am printing a report to a Tally Line Printer and for some reason the line printer is set up for lines per inch 8 and the report prints fine except it is not printing with the lines per inch of 8 but instead the printer is set back to lines per in of 6. Does anyone have any idea what might be getting overwritten with Oracle Reports for the printer to switch to the wrong lines per inch.

I was thinking I needed again to add something to the printer definition file which at this time is the dflt printer definition file but I don't know the syntax to set the lines per inch. Any ideas would be greatly appreciated. This report prints on preformatted paper so it has to be set to lines per inch of 8.

I also had this set as a character mode report but it doesn't matter if I set it up as bitmap or not it runs in either case.

I appreciate it.

shm

 

[nagornyi]

You probably need to look up the printer documentation to see which escacpe sequence is setting appropriate LPI. Then add this to the before report esc clause in the .prt file. Look here for an example:

http://www.fors.com/orasupp/d2k/reports/28399_1.HTM

 

[mcintysh]

Thanks Nagornyi! I found some documentation that had the printer escape sequence for setting the Lines Per Inch. I have never used printer definition files and as you know I have been using it since I was trying to figure out how to print this report without it chopping off so I was using wide180 but turned out it was mainly the paper of US Std Fanfold that stopped that problem. So my question is how do I know that if I put this printer sequence in that it actually is using the prt file defined in the DESFORMAT. I know that my printer definition files are in c:\ORA6I\REPORT60\PRINTERS but how do I know that the report is actually pulling that prt file? I just hate to get back down on site and this not work because it doesn't even recognize that it should pull the prt file. Any help I would appreciate. You have been great.

Thanks.

shm

 

[nagornyi]

I think the report builder (or server) would complain with an error if file specified in DESFORMAT is not found. Try that by specifying some bogus pring file name. To ensure the file is actually used, try making some obvious changes to it that could be easily seen, like set lines per page to 10 or something like.