calebsg

Andy, thanks for the suggestion but it didn't seem to work. Chris, the problem is not the first line of the report but the title of the window in which the report appears. Furthermore it is only seen on global reports.

Caleb

Donald,

Thanks for your reply. I am aware of @CURFUNCT but not aware of how to change the text that appears in the portion of the report window (sent to CRT) which I attached to my previous post.

Thanks,
Caleb

Thank you for your help.

One last (hopefully!) question. I have noticed that the Screen Report Title: XXXXXXXX usually has the function name in the X's as the calling screen and not the name of the report function itself. The latter is much better for diagnostics, obviously.

I searched the docs but couldn't see how/where this was set. Any ideas?

Just added an attachment: in the attached screenshot of the window the report appears in 'PM.DCR' is the name of the screen that called the global report, not the name of the report itself. We would prefer the latter.

Thanks again,
Caleb

After I posted I got wondering and opened up 5.5 VIP (which we don't usually use) and noted that Logic In of the header on a GR is definable, unlike in @MOD. Can anybody confirm that this is also the case for v.6? If so, problem solved!

Thanks,
Caleb

Instead of calling the global report directly you
could call a wrapper global screen which does
SET_RPTOPT and then calls your global report.

Thanks, that would certainly work.

At present we have tools which insert a call to a global screen to set @RPTOPT in Logic In of a non-Global report. Nice and simple as we're using the same global over and over for this..

I noticed when fiddling that the logic in on a Global Report function will also be processed even though you can't actually get to that field in @MOD's @FUN Function Header definition screen. I'm not sure if we can rely on that going forward though.

Regards,
Caleb