schwab rt crystal 14 migration guide and troubleshooting tips product resource...

Schwab Retirement Technologies, Inc. ®

Schwab RT

Crystal 14 Migration Guide and Troubleshooting Tips

Crystal 14 Migration Guide and Troubleshooting Tips June 2016

The material contained herein is proprietary to Schwab and for informational purposes only. The information is not intended to provide tax, legal or investment advice. Schwab does not guarantee the suitability or potential value of any particular information source. Certain information presented herein may be subject to change. The information or material contained in this document may not be copied, assigned, transferred, disclosed or utilized without the express written approval of Schwab.

The Charles Schwab Corporation provides services to retirement plans and participants through its subsidiaries: Charles Schwab & Co., Inc. (Member SIPC), Charles Schwab Bank, Schwab Retirement Plan Services, Inc., and Schwab Retirement Technologies, Inc.® (Schwab RT). Schwab RT is engaged in developing and licensing proprietary retirement plan recordkeeping systems to independent Third Party Administrators.

For further information, contact Schwab Retirement Technologies, Inc. at 4529 Sharon Road, Charlotte, NC 28211, USA. Web site: schwabRT.com.

2016. Schwab Retirement Technologies, Inc. All rights reserved.

Crystal 14 Migration & Troubleshooting

June 2016 Schwab Retirement Technologies of 14

Introduction This guide is provided to illustrate the steps necessary to update your existing CP20 DBF based Crystal Reports, including eStatements, to Crystal Reports version 14 using a Microsoft Access database connection.

This document also provides Crystal 14 troubleshooting tips for issues created by changing the database connection type.

The transition to Access was announced in the alert sent to clients on January 5, 2015 (see next page).

Important!

To help ensure that you have a smooth Q4/2016 year-end reporting and statement production experience, we highly recommend setting aside time now to validate your eStatements and CP20 reports using Crystal 14 and MS Access. Take advantage of our present availability to assist with troubleshooting problems. We plan to prioritize and sequence any critical issues identified by October 14, 2016 into our final 2016 Release scheduled for November. Waiting to migrate to Crystal 14 and Microsoft Access may affect production of your statements or reports if there are any issues.



How to Redirect a Report to Use the New Access Database File Note: The user must use the Crystal 14 icon within Citrix.

1. Open the report using Crystal 14 and save it as a new file with a naming convention (i.e. CR_14) so it is identifiable.

2. Using the new report, go to Set Data Source Location under the Database menu option.

3. Use the OLE DB (ADO) connection option and select the Microsoft Office 12.0 Access Database Engine.



4. Populate the Connection Information.

a. Specify the Data Source which is the location and name of the Access database. Locate the Access database, which can be created by running Statement Generator/CP20 and saving the data file. The default location is the work folder of the operator who saved the data.

b. Select the Access from the Office Database Type dropdown list.

c. Click Next.



5. No other information is needed. Click Finish on the screen shown below.



6. Change the DBF location to point to the new MS Access table.

a. In the top window, highlight the DBF file used in the report and select the corresponding Access table from the bottom window. Select Update.

b. You must do this for each table in the report. If you encounter issues with mapping, see the troubleshooting section of this document.

c. Click the refresh button and the data will be populated.

7. Test the reports in Statement Generator CP20. If you encounter errors when running the report in CP20 module, see the troubleshooting section of this document.



Troubleshooting Crystal 14 Report Conversions

Problem: When mapping, I am prompted that the fields do not exist. Solution: This is most likely caused by a case sensitive field such as BEGDT_DT or ENDDT_DT. Do the following:

1. When the following screen appears, uncheck Match Type at the right and find the appropriate field such as ENDDT_DT, which would now appear as EndDt_dt.

2. Click the Map button.



Problem: I have received the following error message.

Solution: Do the following: 1. Go to Database > Database Expert and select the Links tab.

2. Select the link “line” and right click to select Link Options.



3. Change the Left Outer Join to be an Inner Join

4. You may have to look at each sub-report to find the offending link exception.



Problem: After the report has been refreshed and is populating with data, source names are repeated in the source summary, as shown below:

Solution: Do the following: 1. In Crystal Reports, go to the Design view. right click on the first group, and select Change Group.

2. Change the group order to in ascending order if the order was previously set to in original order.

Note: This step may need to be repeated in the sub-reports.



Troubleshooting Group Changes Problem: I have received the following error message:

Solution: In Crystal Reports, update the Datasource location as noted in the beginning of this document. Problem: I have received the following “Error in formula” message:

Solution: Modify or add the missing parameter link:

1. Click Edit/Subreport Links from the top menu. The following window appears:



2. Click on the subreport in question under For Subreport and make sure you have fields listed under the Field(s) to Link to box. If you do not see the fields listed and need assistance, contact Schwab RT via the customer portal and include the error message, name of report, and location of the report.

schwab rt crystal 14 migration guide and troubleshooting tips product resource...

Documents