Notes

Crystal Reports 2020 is a 64-bit application which requires the use of 64-bit DSNs. You can't create a database link with the 32-bit ODBC Timberline Data Source DSN. You can still use Crystal Reports 2016 for 300 CRE reports that link to the 32-bit ODBC Timberline Data Source DSN.

Default reports and subreports that pull information from the accounting database use the Timberline Data Source DSN. Custom reports can also use this DSN. This allows the report designer to make the report easily portable between users and databases and access built-in reporting features.

Verify the DSN setup

Billing invoice formats

Set up an ODBC TS Billing Field Names DSN. Continue to the Datasoure/Database steps below when completed.

Other Crystal reports in Sage 300 CRE

1. Log on to a workstation or server with both Sage 300 CRE and Crystal Reports installed.
2. Go to Windows Start, Windows Administrative Tools, ODBC Data Sources (32-bit).
3. Select the User DSN tab.
4. Select Timberline Data Source.
5. Click Configure.
6. Click Select Folder.
7. Select the accounting data folder then click OK.
8. Click Options.
9. From the Table and Field Naming list, select Standard descriptions.
10. Select the Use maximum table segment size check box.
11. Click OK to exit the Timberline Data ODBC Setup window.
12. Click OK to exit the ODBC Data Source Administrator window.

Set Datasource Location and Verify Database in Crystal Reports

Set Datasource Location

1. In Crystal Reports, open the report.
2. From the Database menu, select Set Datasource Location.
3. In the Current Data Source section, expand the Report section.
4. Select Timberline Data Source (or TS Billing Field Names for BL invoice designs).
5. In the Replace with section, expand My Connections.
6. Select Timberline Data Source (or TS Billing Field Names for BL invoice designs).
   • If Timberline Data Source (or TS Billing Field Names) doesn’t exist, proceed with these steps:
     1. Expand Create New Connection.
     2. Double-click ODBC (RDO).
     3. In the Data Source Name section, select Timberline Data Source (or TS Billing Field Names).
     4. Click Next.
     5. If you’re using Sage 300 CRE security, enter a User ID and Password when prompted. The user must have ODBC Read access. The user must have appropriate access for Record and File Security, if activated.
     6. Click Finish.
     7. In the Replace with section, select Timberline Data Source (or TS Billing Field Names).
7. Verify the data source still shows in the Current Data Source section.
8. Click Update.
9. Repeat these steps for the Subreports section, if present.
10. After you set all data sources, click Close.
11. Sometimes, using Update on the Timberline Data Source connection isn’t sufficient to update all the individual tables. If "table note found" errors occur when running the report or using Verify Database, update the individual tables.

(Optional) Set Datasource Location on individual tables

1. From the Database menu, select Set Datasource Location.
2. In the Current Data Source section, expand the Report section.
3. Expand Timberline Data Source.
4. Select the first table listed.
5. In the Replace with section, expand My Connections.
6. Expand Timberline Data Source.
7. Select the same table name that you selected in step 4.
8. Click Update.
9. Repeat steps 2 through 8 for each table.
10. Repeat these steps for the Subreports section, if present.
11. After you update all tables, click Close.

Verify Database

1. From the Database menu, select Verify Database.
2. If you receive the following messages:
   • The database file "[table name]" has changed. Proceeding to fix up the report: Click OK. Then click OK to the message "The database is now up to date." The messages appear for each table that's changed since the report creation or last update. Table names may repeat for subreports.
   • The database table "[table name]" cannot be found. Proceed to remove this table from the report: Select No to each message. Then perform the steps above in the (Optional) Set Datasource Location on individual tables section. You can do this for just the table names referenced in the errors.
3. Repeat Verify Database to verify this error no longer occurs.
4. Save the report under File, Save.