Hi Naomi,
CodeRep works pretty simillar to FRX engine but instead of interpreting
report expressions from each band, CodeRep class directly executes
code stored in event methods respective to frx structure.
So as you wld place expressions in report bands of frx,
here you wld write respective code to make that writing/printing happen.
CodeRep class will just make sure that report events take place
when they are supposed to.
Typical CodeRep implementation for TXT output format, would look somewhat like this;
define class myReport as txt_report
.
.
procedure report_setup
this.r_alias = yrDrivingAlias
declare this.r_GrpExp(2)
this.r_GrpExp(1)= yrGroupCondition1
this.r_GrpExp(2)= yrGroupCondition2
.
.
procedure PageHeader
? '---- ------------------------- -------'
? 'Code Name Value1 '
? '---- ------------------------- -------'
procedure GroupHeader1
? cGroupExpression
? '-------------------------------------------'
procedure Detail
? table1.Code
?? table1.Name at 5
?? table1.value1 at 31
.
etc
.
.
enddefine
You can convert relatively easily ordinary DOS frx reports using this
class, but If I understood correctly this report hv to print in preprinted forms.
In this case it might be easier for you to do it straight forward with ordinary code (set of procedures) printing directly to dotmatix with ?/?? , then having to learn class functionality & play by its rules.
Rgds++
Sergio
>Hi everybody,
>
>That's a continuation of the thread I posted few days ago. I guess my manager bought the idea of converting that report into @SAY commands for better control. My qyestion is: how to ease that conversion? What class is available, what can help?
>
>I know there are two classes: one by Hilmar and another by Srjdan. I never tried any of them. What exactly they are doing and should I get one of them (which one) to get that job done as quickly as possible. So far we're talking about one particular not extremely complicated report.
>
>Thanks in advance.