Rave has maintained a very high backwards compatibility with older versions so we don't expect you to have any problems. These are the two issues our customers sometimes have when upgrading from older versions of Rave:
1: I can't remember exactly when this was done but some class names were changed but we include calls to RegisterClassAlias to handle those changes for components in the DFMs automatically. If you are creating any of these components in code you'll need to use the updated class names. Here they are listed below if you want to check your code before upgrading (new class first, old class name second):
RegisterClassAlias(RpRave.TRvProject, 'TRaveProject');
RegisterClassAlias(RpSystem.TRvSystem, 'TReportSystem');
RegisterClassAlias(RpFiler.TRvNDRWriter, 'TReportFiler');
RegisterClassAlias(RpCon.TRvCustomConnection, 'TRPCustomConnection');
RegisterClassAlias(RpConDS.TRvDataSetConnection, 'TRPDataSetConnection');
RegisterClassAlias(RpConBDE.TRvTableConnection, 'TRPTableConnection');
RegisterClassAlias(RpConBDE.TRvQueryConnection, 'TRPQueryConnection');
RegisterClassAlias(RpRenderPDF.TRvRenderPDF, 'TRPRenderPDF');
RegisterClassAlias(RpRenderHTML.TRvRenderHTML, 'TRPRenderHTML');
2: It is recommended that if you have any visually designed reports (.RAV files) that you load those projects up in the new Rave designer, recompile any scripts using the compile button (if you used scripting) and then re-save the projects (they will automatically be saved with any updated file format changes).
That's pretty much all that has been reported to us from other customers upgrading from older releases.
We are not offering upgrade prices from previous versions of Rave since it has been 5 years since our last major release.
Please let us know if you have any additional questions.
Partager