If you use the COM version of ActiveReports and would like to migrate to the .NET platform and use ActiveReports 11, you are in the right place. You can pull all of your layouts in, leaving only the code to update manually. The process is, basically, save, load, update code.
In order to migrate reports created in the COM version of ActiveReports (ActiveReports 2.0) to ActiveReports 10, you must first save older designer files (DSR or DSX) as RPX files in the ActiveReports 2.0 Designer to a format that we can import into the new version of ActiveReports. Here are the steps to convert ActiveReports 2.0 files to RPX at design time:
You can also save it at run time using VB6 code like the following:
Private Sub cmdSave_Click() rptRDFs.Run rptRDFs.SaveLayout App.Path _ & "\\rptRDF.RPX", ddSOFile cmdLoad.Enabled = True cmdSave.Enabled = False End Sub
Save the report and run it. Either of these methods lets you save the file with an .RPX extension that you can load into a new Section report.
NOTE: It's important that you load the RPX into a new report, because loading an RPX file wipes out any existing layout. Here are the steps to load the RPX into a new Section report:
Learn more about how to Save and Load RPX Files.
ActiveReports does not import Visual Basic code or script into .NET. You will have to rewrite VB script to fit .NET language specifications. You may also need to update data sources to modern ones (for example, Microsoft.Jet.OLEDB.3.1 to Microsoft.Jet.OLEDB.4.0). If you used code or script in the report, you can find the new API members in the ActiveReports 11 Class Library documentation.