Adding a New Data Source Name

 

The most common problems experienced occur immediately after installation as a result of an incorrectly installed database or Data Source Name (DSN). A Data Source Name is used by ODBC (Open Database Connectivity) drivers, which connect a program to a database. This works much like a printer driver, which connects a program to a printer. If ODBC errors are reported by the program, then the following steps should be taken to verify that the DSN for your program is correctly configured.

  1. Determine the DSN for your program. See Configuration Settings for this information.
  2. Click on “Start” and then “Run”. A dialog box should open up which will allow you to enter a command to execute. In the space provided, type “odbcad32” (without the quote marks) and press Enter.
  3. The ODBC Data Source Administrator should appear. The screen should look similar to this:

 

Figure 1: ODBC Data Source Administrator

 

  1. Click on the “System DSN” tab and then click on “Add…” The following screen will appear:

 

Figure 2: Create New Data Source

 

  1. Click on “Microsoft Access Driver (*.mdb) and click “Finish”

 

 

Figure 3: ODBC Microsoft Access Setup

 

  1. Enter the DSN You found in Step 1 in the “Data Source Name” field. Click on “Select”, which will open up a “Select Database” dialog. This will look similar to this:

 

Figure 4: Select Database

 

  1. Using the provided controls, navigate to the location (on your computer or on your network) where the database was installed. Refer to Configuration Settings for the name of the database file used by your product. You should find the file at this location. If you do, click on the file and then “OK”.
  2. The previous screen, “ODBC Microsoft Access Setup” will appear. Click OK.
  3. The previous screen, “ODBC Data Source Administrator” will appear. Click OK.

 

Try running your program again. If you were experiencing a problem caused by an incorrectly configured Data Source, then the program should work normally. If you experience more ODBC errors, refer to TroubleShooting Procedures.