Functions in Report Layout memo tab

Does anyone on here use the facility, in the Opera 3 Report Layout form, to write one or more functions that can be called from the associated report.

I have a bespoke customer report, for which I wrote a function fred() within the memo tab of the Report Layout form.

I called fred() from the report, and all was working correctly, the report displayed the return value from fred().

I then added a second function - bill() - to the Memo tab, ran the report, and it crashed with "File 'fred.prg' does not exist".

I removed the second function - bill() - from the Memo tab, leaving only fred(), which used to work fine, ran the report, and received the same error message.

Now the report continually crashes with this error.

I have a similar problem with another bespoke report, in which the report crashes with the "file does not exist" error, relating to the function name.

Conversly, I have several other bespoke reports where the function in the memo tab works perfectly when called from the associated report.

Any thoughts

Much appreciated

Steve

Find more posts tagged with

Pegasus - Partner General Discussions

Comments

alan-bourke

Steve

I think what Opera (specifically the Publisher) does is take your code from seqrplay.do_repfunc field and wraps it in an ImpactPrinter function declaration like this:

Function ImpactPrinter

Return

Then on the layout you would call ImpactPrinter() with any parameters needed.

But in your example it will end up something like:

Function ImpactPrinter

   Function Bill()
       ? "Bill"
   EndFunc

   Function Fred()
       ? "Fred"
   endfunc

Return

However that won't compile which might be the problem. So I think basically your code for this needs to be one function (see the seqrplay entry for report sqwgsr4fv5b_xls)

Steve Loader

Thanks Alan, that is very useful.

Do you know if this functionality is documented anywhere?

It seems quite strange that my previous attempts at writing report functions worked okay (albeit probably more by luck than judgement). Even my fred(0 function worked, until I added function bill(), and then it never worked again.

Anyway, I toook a look at the code for report sqwgsr4fv5b_xls and, on that basis, I guess that if I want write multiple functions for one report, then my code should look something like:

Lparameter lnAction

DO CASE

CASE lnAction = 1

My code

RETURN

CASE lnAction = 2

My code

RETURN

CASE lnAction = 3

My code

RETURN

ENDCASE

RETURN

Do you concur?

Thanks again

Steve

alan-bourke

Steve

I'm not aware of it being documented, it could be in the reporting courseware I suppose.

Yes I think the DOCASE approach is the way to go unless you want to get into writing bespoke.

Steve Loader

Morning Alan,

Before I resort to asking Pegasus, can I pick your brain one more time please?

I looked at various Opera 3 standard reports that contain the ImpactPrinter function call, and so have amended my report as follows:

The report contains a field with the expression "ImpactPrinter(.T.)."

The Memo tab of the associated Report Layout entry contains code similar to the following:

lParameters Action

My code

Return

However, when I run the report, I get error "File 'impactprinter.prg' does not exist".

Clearly I've made a howler somewhere, but I can't see the obvious difference between the Opera 3 standard report use of ImpactPrinter, and mine?

Much appreciated

Steve

Copyright © 2025 Infor. All rights reserved.