Setting up 64-bit DSNs for PO/IV for use with Crystal Reports 2020
Description

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 released only 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.

Instructions for versions 26.1 and later

Cause
Resolution

Complete all steps outlined below to create the DSNs.

Ensure 300 CRE creates the 32-bit User DSNs

  1. Start and then exit both the Purchasing (PO) and Inventory (IV) 300 CRE applications.
  2. Open the ODBC Data Sources (32-bit) Control Panel utility.
  3. Confirm you see 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
  4. The names of these DSNs are among those used by various canned PO/IV reports. Crystal Reports 2020 can't use these DSNs.

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 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 DSNs 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 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.

Running the Purchasing (PO) and Inventory (IV) 300 CRE applications will cause the creation of the 32-bit User DSNs. After running PO or IV, complete the steps above again before running Crystal Reports 2020.

Steps to duplicate
Related Solutions