Instant Guide

Instant Guide Code

ICCL

Feedback

Forums

Articles

Contact

About Us

Friendly Sites

ODBC Connections

A Name is
a Name. In using Crystal Reports in a development environment, the biggest problem I have run into is ODBC naming conventions.  Using the same name for a database will reduce problems for report developers, whether it's accross a large enterprise or a single development to production server.

A rose by any other name ...

would smell as sweet.  But just a slight typo will stop a report from running.  I recommend you especially verify the odbc connection on the server matches your development box.  I'm going to give a quick example of how to make and ODBC connection.  There are a lot of database types out there, I'm going to illustrate using a SQL server connection.  Some of this will depend on what operating system you are on.  I am assuming you are on 2000 or XP.

• Start - Control Panel - Administrative Tools
• Select Data Sources
• In the Odbc Data Source Administrator, Select System DSN
• Click the Add... button


• 
  In Create New Data Source, Select SQL Server
• Click the Finish button.


• 
  Type the name you will refer to this connection as in the Field next to Name.  Don't type in any spaces or special characters.  The computer can handle them, but it inspires Typos in people.  This is the name you need to be the same between Development and Server. 
• I usually skip the description, but you can fill it in to help remind you why you made this connection.
• Type in the Name or IP address of the SQL server you will be using.
• Click the Next Button.


• 
  I recommend using SQL server authentication and using a common username in development and production.  It removes one more thing that could go wrong.  Also keep the obtain settings box checked.
• (Optional)Click client configuration and check TCP/IP and dynamically assigned port (unless your server is installed differently)  The server alias and server name should be populated automatically.  Click OK.
• Type in the username and password you want to use.
• Click the Next button.


• 
  Check the Change the default database to and pick your database from the dropdown.  If its not here, you have a problem.  Go back and make certain everything is typed in correctly.  If it is, check with your administrator to be certain your username has access to the database.
• After you successfully pick your database from the dropdown, Click the Next button. 


• 
  Leave the defaults on the next page and Click the Finish Button.
• On the ODBC Microsoft SQL Server Setup window, Click the Test Data Source.  If it works you are ready to go.
  If not your have some troubleshooting to do.  Press the OK Buttons to exit this window.


• Now you should have a new System DSN listed in your ODBC Data Source Administrator window.  The name you see will be what you use exactly as it is typed. 
 

Repeat on the Server

Repeat these steps on your deployment server using the exact same name.  You will probably need to be logged in as an administrator to create an ODBC connection.