Hello All,

When I want to produce a report on screen,I normally perform a select and then call up a report from the banded report writer.

As I have a rather intricate report which requires it to read data from tables that aren't attached (I have their file handles logged), so I have had to hard code the report.

I am using init.view and everything seems fine until I get to the bottom of the report. It then tries to automatically jump out of the report and back to the calling program. If I press the key at this point, I actually get back to the report less its border. It is now stable and I can page up and down it fine (but it looks crap). what am I doing wrong? Am I terminating my report program incorrectly?

I have created the report as a stand alone program and call it from a subroutine after a select is performed.

I get the same results if I run it from TCL

P.S. Headers & Footers are set to ' '

Any suggestions would be warmly welcomed

Claude

Claude,

To point out your error, first start with a simple version of init.view and then add features to see where your code is not right.

It could look like this before entering the loops:

(processing)…

report_width=150

call init.view(report_width)

@view.mode=1

heading "Test report"

(continue processing…..)

Things that may go wrong are:

- wrong sequence of commands

- report width exceeds actual width

- statements to the printer while printing to screen

I hope it helps

Regards

Wilhelm

Claude ..

Be sure to call INIT.VIEW before you initialize any headings or footings or set any columns. Sometimes it helps to call VIDEO.RW before and after to save and restore the underlying screen. HTH

Don Miller

C3 Inc.

Claude,

I had a problem similar to yours. I was invoking a subroutine from a menu, and then subroutine used INIT.VIEW to display a report.

The only way I could fix it was to write a wrapper around the subroutine that was a straight program.

Then, I changed my window to run the program, which called the subroutine. This fixed my problem.

Best of luck,

Matt Sorrell

msorrell@movgal.com

Thanks all for your help,

You pointed out subtle facts that I hadn't seen clearly, namely that there were variables from the subroutine passed to the report. I simply saved the details to a file performed the stand alone routine which read the details from the file and hey presto… Stability.

I probably could have used arev common as well

Thanks & Regards

Claude

View this thread on the forum...