I wish the following TCL sentence would produce a real landscape report:

LIST FILE HEADING "'{LANDSCAPE}'" FOOTING "'{RESET}'" FIELD

Where the VOC symbolics EXECUTE the appropriate SETLPTR commands (or set @LPTRHIGH/WIDE) and set @ANS to the printer's escape sequence.

The printer sequences do their bit but the SETLPTR doesnt.

I think from reading other postings that the SETLPTR has to be called a calling program, any way to get this TCL line working??

You could have a symbolic return the landscape codes at the start of each row of the report. Say CHAR(27):CHAR(x):CHAR(y):CHAR(z) is your landscape code setting for your printer, then put a symbolic SET.LANDSCAPE in DICT.VOC with a formula

return CHAR(27):CHAR(x):CHAR(y):CHAR(z)

Ensure the length of the SET.LANDSCAPE item is adequate.

If you need to restrict this to the start of the report only use something like:

IF @REC.COUNT < 1 THEN

ANS=CHAR(27):CHAR(x):CHAR(y):CHAR(z) 

END ELSE

ANS='

END

RETURN ANS

The above is untested but it may be a starting point for you.

steve@state-of-the-art.com.au

Thanks Steve,

I have the escape sequences working, so the printer goes into compressed landscape, but I cant get RLIST to do less and longer lines per page, as it seems SETLPTR and @LPTRWIDE/HIGH are not effective inside a symbolic enbeded in the heading, or anywhere else in the report?

Can you think of any way a RLIST report can sucessfully change the lines per page. I dont really want to call all reports from a program to do this.

Can you (or anyone else) help?

Perhaps a PERFORM statement in place of EXECUTE will work. Otherwise you could add a new TCL item in the VOC file using the REPORT_NAME as its ID.

Field 1 in the VOC record is: TCL

Field 2 is: SETLPTR width ,height

Field 3 is: LIST FILE HEADING "'{LANDSCAPE}'" FOOTING "'{RESET}'" FIELD

Then you can simply run the report at TCL as: REPORT_NAME

Bill

Yes, thanks Bill, this is probably the only way.

And it doesnt involve writing a program to call each report.

Phil,

The RLIST statements can be placed in a VOC with sequential entries,

eg.

TCL

PDISK….

SETLPTR….

LIST…..

The other option is to run a setup step as a VOC command,

then ensuing reports. Users know to type HP.CONDENSED then HP.LANDSCAPE then LIST…etc.

There may be other ways, but they don't occur to me right now.

steve@state-of-the-art.com.au

View this thread on the forum...