Set up SQL Data connections for Sage Crystal Reports

Set up SQL Data connections for Sage Crystal Reports

32 Bit DSN Manager

1. Create a DSN pointing to the SQL Database.



2. Connect to Sage SQL Server and Instance that has anterraDataCenter database.


3. Use Windows Authentication.



4. Change the database to your anterraDateCenter database.



5. Use Defaults here.



6. Test Data Source.



Crystal Reports

1. Select new DSN in Data Source Selection.



2. Checked Trusted Connection.



3. Test Report in Crystal Reports Designer.



4. Add the report to Sage as normal.  Select the Crystal Report design, but do NOT check the 'Use SQL' check box.



5. Test the new report in the Sage menu.




    • Related Articles

    • Sage 300 CRE Upgrade Guide for anterraDataCenter

      Background Upgrading Sage 300 CRE to V17 or V18 can interrupt ADC syncs and disable your Windows Server Scheduled Tasks. We have prepared this guide to assist you in upgrading anterraDataCenter and preventing sync and scheduled task outages.  Please ...

    • Troubleshooting Problems Data Sync to AnterraBI

      Some of the common reasons for the anterraDataCenter sync to stop running are as follows: The local or active directory account that is used by Windows Task Scheduler to run the data update has had its password changed. Your ERP system (Sage, ...

    • Invoice Sync: Setup Sage 300 CRE with ADC

      Once you have Invoice Sync installed, use the following steps to complete setup. Configuring Sage 300 CRE with ADC Clicking the Config menu (shown below) then choosing Setup ADC Sage 300 CRE will bring up the Config ADC Sage 300 CRE window. In the ...

    • 'Timberline Version Changed' appears when anterraDataCenter opens

      Background When anterraDataCenter opens, a dialog box with the title "Timberline Version Changed" appears Each time anterraDataCenter opens, a message appears that has the following text in it: "Timberline version has recently been updated. SQL ...

    • Resolving Pervasive.SQL 3006 error found in AnterraDataCenter Log files

      The Pervasive.SQL.3006 error is a result of a timeout between the Pervasive Client and Server which creates a broken or interrupted connection. This can happen if AnterraDataCenter is on a different server from the Sage Pervasive database, or if the ...