Only perform these steps on the machine where a user intends to run reports from within the Crystal Reports 2020 application. Crystal Reports 2020 is only available as a 64-bit application, so it requires 64-bit DSNs as report data sources. Crystal Reports 2020 can’t use 32-bit DSNs as report data sources.

You don't need to create these DSNs to run reports from within 300 CRE applications.

You only need to complete these steps on the 300 CRE client machine. Sage automatically creates the 64-bit “Timberline SM Data” DSN on the server.

Instructions for versions 26.1 and later

• Setting up 64-bit DSNs for SM and Crystal Reports (v26.1 and later)

Complete all steps outlined below to create the DSNs.

Ensure that Sage 300 CRE creates the 32-bit User DSNs

1. Start Service Management (SM).
2. Run Reports, Sales, Active Leads.
3. Then exit Service Management (SM).
4. Open the ODBC Data Sources (32-bit) Control Panel utility.
5. Confirm you see this 32-bit DSN on the User DSN tab:
   • Timberline SM Data - referencing data in the SMData subdirectory of the recent Company Data Folder
     

The names of these DSNs are among those used by various canned SM reports. Crystal Reports 2020 can't use these DSNs.

Create Corresponding 64-bit System DSN

For the Timberline SM Data User DSN:

1. Select the DSN within ODBC Data Sources (32-bit) on the User DSN tab and click Configure. Keep this window open for reference in the next steps.
2. Within ODBC Data Sources (64-bit) click the System DSN tab and click Add.
3. Select Pervasive ODBC Interface and click Finish.
4. Copy the Data Source Name from the same field in the ODBC Data Sources (32-bit) window.
5. Copy the Server Name/IP from the same field in the ODBC Data Sources (32-bit) window.
6. Click Get List.
7. Select the Engine DSN name as the Database Name value.
   
8. Click Test. Click OK to the “Connection successful!” message.
9. Click OK to close the Add window.

Delete the 32-bit DSN created by 300 CRE

Attempting to run a report at this point from within Crystal Reports 2020 will fail. This occurs due to the existence of the 32-bit User DSNs with the same names as the 64-bit System DSNs. To run a report within Crystal Reports 2020, first delete the 32-bit User “Timberline SM Data” DSN.

For the User DSN listed above:

1. Select the DSN within ODBC Data Sources (32-bit) on the User DSN tab and click Remove.
2. Click Yes to confirm.

Running the Service Management (SM) 300 CRE application will cause the creation of the 32-bit User DSNs. After running SM, complete the steps above again before running Crystal Reports 2020.

Optional: Changing your Service Management dataset

If you switch to a different dataset than you used to create the 64-bit DSN, update the 64-bit “Database Name” to use the new dataset.

1. Start Service Management (SM) on the client.
2. Run Reports, Sales, Active Leads.
3. Exit Service Management (SM).
4. Open Timberline SM Data DSN in the User DSN tab of the ODBC Data Source Administrator (32-bit).
5. Open Timberline SM Data DSN in the System DSN tab in the ODBC Data Source Administrator (64-bit).
6. Click Get List.
7. Change the 64-bit SM DSN’s Database Name setting to match the 32-bit User SM DSN.