- Getting Started
-
Administration Guide
- Get Started with Administering Wyn Enterprise
- Configuration Settings
- Account Management
- Security Management
- System Management
- Document Management
-
How To and Troubleshooting
- Change Default Password
- Set Language Preference
- Slack Integration
- MS Teams Integration
- Create Custom Language Packages
- Configure Identity Server
- Configure Single Sign-on
-
Convert Crystal Reports/MS Access Reports to Wyn Reports
- Encrypt or Decrypt Connection Strings
- Using ClickHouse as OLAP Database
- Hide Download Link in Scheduled Tasks
- Configure Redis Cluster using Username and Password
- User Guide
- Developer Guide
Convert Crystal Reports/MS Access Reports to Wyn Reports
You can convert a Crystal Reports report and/or a Microsoft Access report to Wyn Reports by running the ActiveReports Import Wizard.
Converting Crystal reports/MS Access Reports in the ActiveReports Import Wizard
Run the ActiveReports Import Wizard. The wizard can be run from the start menu or by executing GrapeCity.ActiveReports.Imports.Win.exe from C:\Program Files\Wyn Enterprise\Tools\ActiveReportsTool location.
In the ActiveReports Import Wizard that appears, click Next.
Choose Microsoft Access (mdb or accdb) or Crystal Reports (rpt) as the input format and click Next.
Click the ellipsis button to browse to the location that contains the files that you want to import. A list of files that you can import appears.
Select the reports to import, click Open, and then click Next to analyze them.
Use the ellipsis button to select a destination folder to store the converted reports. Also select an output format (Section Report, Page Report or RDL Report or Both) for each report in the Output Format column.
Click Next to start the conversion.
Once the conversion process is complete, click Finish to close the wizard and go the destination folder to view the converted reports. You may optionally leave the check on for the Open Log file checkbox to see the results log.
The import wizard converts reports to the closest possible format, but due to differences between products and versions, the extent to which your reports are converted depends on your specific report layout. You may have to partially redesign the report and add script or code to get the same output as Microsoft Access Reports or Crystal Reports.
When converting to Page Reports or RDL Reports, whether a report is imported as a Page Report or RDL Report, depends on the following factors:
• If a report has a single detail section it is imported as a Page Report.
• If a report has a CrossTab control and its layout is composed of multiple sections it is imported as an RDL Report.
Note: Sections in a report appear as BandedList.
Please refer to the additional information below, to understand the conversion process in detail.
Importing Crystal Reports
To convert Crystal Reports, you need to install Visual Studio and Crystal Reports for Visual Studio on your machine. The supported versions of Visual Studio and corresponding Crystal Reports are as follows:
Visual Studio | Editions | Crystal Reports | Assembly Version |
---|---|---|---|
2008 | Professional, Team System | Crystal Reports for Visual Studio 2008 | 10.5.3700.0 |
2010, 2012, 2013, 2015, 2017, 2019 | ... | SAP Crystal Reports, developer version for Microsoft Visual Studio | 13.x.x.x |
Crystal Report controls are converted as follows:
Crystal Report | Section Report | Page Report/RDL Report | Note |
---|---|---|---|
Box | Shape | Container | The LineWidth property and rounded boxes are not imported. If the Box control extends to multiple sections, the box is imported as line controls. |
CrossTab | Subreport | BandedList | CrossTab control is not imported as it is. |
Line | Line | Line | The size of Dot and Dash (the LineStyle property) is not the same as the original report. |
Subreport | SubReport | Subreport | Set the subreport in code after conversion. |
TextObject | Label | Textbox | Only page number, total page, page n of m in Special Fields are imported. |
FieldObject | TextBox | Textbox | Only page number, total page, page n of m in Special Fields are imported. |
Picture | ... | Container | Picture object is not converted. |
Importing Microsoft Access Reports
To import Microsoft® Access® reports, you must have Access 97, 2000, 2002, 2003, 2007, 2010, or 2013 installed on your system.
Microsoft Access report controls are converted as follows:
Microsoft Access Report | Section Report | Page Report/RDL Report | Note |
---|---|---|---|
Rectangle | Shape | Container | Controls placed inside the Rectangle control are also imported along with the parent control. |
ChekBox | Label | Textbox | ... |
Image | ... | Image | Image control is not converted while converting to a Section Report. |
Label | Label | Textbox | ... |
Line | Line | Line | ... |
Page Break | PageBreak | Container | In Page Reports and RDL Reports, the PageBreakAtEnd property is automatically set to True on importing a Page Break control. |
Subform/Subreport | SubReport | Subreport | ... |
Limitations in Crystal Report/MS Access conversion
• Any controls, functions, and text formats which are not supported by Wyn Enterprise are not imported.
• The shadow property of a control is not imported while converting a report.
• The OLE object is not imported as it is treated as PictureObject in the object structure of Crystal Reports.
• In Microsoft Access reports, VBA code appears in as commented statements in script. You have to modify the code after importing.