Going between RB versions

ScottStalheim · April 2021

I have RB Enterprise, and I am now working with another software developer who has RB Standard. As far as I can see from the feature matrix, I am using 2 features not in RB Standard, namely RAP code, and the REST Email component. If I share all my code with the other developer, I wonder what issues may arise. My theory is that:

1. Regarding the RAP code found in the Calc tab of the report designer, the program will compile for the Standard version uset, but they will have no access to the Calc tab or the RAP code. However, I can move code out of RAP and use the RBUilder events to do the same operations in Delphi. In other words, I can delete code in RAP and put it in Delphi using the report events so they can see and modify the code as they wish. Code that looks like:
procedure TXRepPerfCows.DBTextEligNumGetText(Sender: TObject; var Text: string);
begin
if ppDBPipeline1['numElig'] = 0
then DBTextBredNum.Visible:= False
else DBTextBredNum.Visible:= True;
end;

2. In the case of EMail REST components added to Delphi, perhaps they will have to be removed in order for the code in Delphi standard to compile.

Thanks for any insight...

Scott S.

nicocizik · April 2021

Hi Scott,

1. All RAP code and components will need to be removed. If a report contains RAP code, it will not generate in the Standard version of ReportBuilder as the RAP compiler is not included in that edition. You will also need to be aware that when loading templates, event handlers in Delphi may need to be re-assigned.

2. The REST email components are included in the Standard version of ReportBuilder. Our cross platform FMX REST client/server components are not.

- Note that the Standard edition of ReportBuilder also does not include the following:

1. DADE: Report level data access (Data Tab).
2. End User: TppDesigner at runtime.
3. Crosstab component.

ScottStalheim · April 2021

Thanks. That will be workable.

ScottStalheim · April 2021

So now that I think that i have removed all RAP and use of DADE from a particular project, i would like to test it myself to see if it work properly using RB Standard (before giving this project over to the other developer). Perhaps removing certain RB units from the uses, or some other way?

nicocizik · April 2021

Hi Scott,

As you mentioned, the best way to test would be to remove any RAP, DADE, CrossTab, and End-User units from your uses clause.

Another option would be to temporarily install the trial edition of RB Standard and test with that.

ScottStalheim · April 2021

So I assume raCodMod for RAP. Is there a list in the help? or anything starting "ra" then?

nicocizik · April 2021

Hi Scott,

ra* - RAP units
da* - DADE units
ppCT* - Crosstab units

ppDesigner, ppEndUsr, etc... - End User units

To be absolutely sure, you will need to test your report(s)/application with the Standard edition (trial), perhaps on a VM.

ScottStalheim · May 2021

So I have set up Delphi on another machine, and now need to install RB Standard on there somehow? My install link and info is set to enterprise.

Also, I see that when I remove all RAP from the calc tab and put the corresponding functionality in the Delphi code, the raCodMod unit is automatically added back to the USES on a few forms, but not most!

Thanks,
Scott

nicocizik · May 2021

Hi Scott,

I suggest downloading the trial edition of the Standard edition from our website to test with. This is the full version of ReportBuilder with limitations. http://www.digital-metaphors.com/download-trial

If raCodMod is being automatically added, there are still RAP references in your application (likely inside the .dfm file). These could be either inside your report definitions or your existing uses clause.

Going between RB versions

Comments