These steps should be performed only on the machine where a user intends to run reports from within the Crystal Reports 2020 application. Crystal Reports 2020 is released only as a 64-bit application and therefore requires 64-bit DSNs be configured which are to be used as report data sources. Crystal Reports 2020 cannot use 32-bit DSNs as report data sources.

These instructions are not needed for allowing reports to be run from within 300 CRE applications.

Step 1: Ensure that 32-bit User DSNs are created by 300 CRE

1. Start and then exit both the Purchasing (PO) and Inventory (IV) 300 CRE applications.
2. Opening the ODBC Data Sources (32-bit) Control Panel utility should now display these 32-bit DSNs on the User DSN tab:
   • Timberline IV Data - referencing data in the POIVData subdirectory of the recent Company Data Folder
   • Timberline PO Data - equivalent to Timberline IV Data
   • Timberline Office Data IV - referencing Accounting data in the root of the recent Company Data Folder
   • Timberline Office Data PO - equivalent to Timberline Office Data IV
3. The names of these DSNs are among those used by various canned PO/IV reports. But, as these are 32-bit DSNs, they cannot be used by Crystal Reports 2020 (unlike Crystal Reports 2016 and earlier which were 32-bit applications that did make use of them).

Step 2: Create Corresponding 64-bit System DSNs

For all four of the User DSNs listed above:

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 on the System DSN tab and click Add.
3. Select Pervasive ODBC Interface and click Finish.
4. Copy into the Data Source Name field the value from the same field in the ODBC Data Sources (32-bit) window.
5. Copy into the Server Name/IP field the value from the same field in the ODBC Data Sources (32-bit) window.
6. Click Get List.
7. Select from the Database Name list the value in the Engine DSN field in the ODBC Data Sources (32-bit) window.
8. Click Test. You should see a message stating “Connection successful!”. Click OK to dismiss this message.
   
9. Click OK to close the Add window.

Step 3: Delete the 32-bit DSNs created by 300 CRE

Attempting to run a report at this point from within Crystal Reports 2020 will fail due to the existence of the 32-bit User DSNs which have the same names as the 64-bit System DSNs created above. Therefore, in order to successfully run a report within Crystal Reports 2020, we must first delete all of the 32-bit User DSNs listed above.

For all four of the User DSNs 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.

Important: Running the Purchasing (PO) and Inventory (IV) 300 CRE applications will cause the 32-bit User DSNs to be recreated. Therefore, after running PO or IV, the steps above will need to be performed again prior to running Crystal Reports 2020.