Setting Up ODBC 

ODBC Definition: Short for Open Database Connectivity, a standard database access method developed by SQL Access group in 1992. The goal of ODBC is to make it possible to access any data from any application regardless of which database management system (DBMS) is handling the data. ODBC manages this by inserting a middle layer, called a database driver, between the application and the DBMS (the Firebird database for DBA). The purpose of this layer is to translate the application's data queries and commands that the DBA Firebird understands. For this to work, both the application and the DBA Firebird database must be ODBC-compliant.

Warning: ODBC is meant to be used as "read only" access to our database. Writing to our data tables can cause irreparable harm. Please refer to the rules and restrictions section in the following document.

DBA Data Dictionary

DBA does not come with a built in ODBC driver. In order to communicate with other databases or applications that are ODBC compliant you will need to install an ODBC driver for the Firebird/Interbase database. The following ODBC driver is recommended.

Link for Firebird_ODBC_2.0.0.151_Win32.exe

(Note: If clicking the above link does not work, click on the link from the Firebird SQL Downloads page)

Step One: Download and Install an ODBC Driver

  • Download the ODBC driver above and follow the instructions from the developer.

Step Two: Setup ODBC on your Windows Server or Workstation

Contol Panel/Administrative Tools/Data Sources (ODBC)

Go to Control Panel/Administrative Tools/Data Sources (ODBC)

  • Select System DSN Tab
  • Select Add
  • Select the Firebird/Interbase ODBC driver you previously installed.
  • Type a Data Source Name (DSN) such as DBA NG.
  • Specify the new Firebird driver. This should prefill from your previous selection.
  • Browse and select the path to the DBA system database file. This is your ejdb.fdb file and should be located in the database folder of your DBA Manufacturing program directory. You will need to also include the name of the server (or your PC if a standalone install) and a colon before the path (see the example above)
  • Enter Database Account name = SYSDBA
  • Password = masterkey
  • Test the connection

Special Instructions for Client Workstations

If you are at a workstation and the database is on a server, you will need to use the local Database path on the server. You will also need to add the server name and a colon before the path. An example would be:

SERVER:C:\Program Files\DBA Manufacturing\Database\ejdb.fdb.

You will also need to copy the FBCLIENT.DLL file from the Firebird\Firebird_1_5\bin directory from the server onto your local PC, and reference that file in the CLIENT field in the ODBC setup. In the example above, we copied the file to the C:\DBA Help folder on the local workstation.

Using ODBC on 64-bit Windows Platforms

Note: Do NOT install a 64-bit ODBC driver. Only install the 32-bit driver listed above.

32-bit ODBC drivers are available to 32-bit applications running in the WOW64 layer, but not to 64-bit applications.

On 64-bit Windows platforms, there is both a 32-bit and a 64-bit version of ODBC Administrator. The 64-bit ODBC Administrator is located in the standard location: Administrative tools in Control Panel. The 64-bit version of the ODBC Administrator only lists 64-bit ODBC drivers and data sources.

To work with 32-bit ODBC driver data sources on 64-bit Windows, you need to use the 32-bit ODBC Administrator. To run the 32-bit version of the ODBC Administrator, in the Windows Run dialog box, type:


WARNING: Do not edit database tables!!!

Under no circumstances should any DBA Next-Generation table be directly edited using DB Console or any other tool. THIS CAN CAUSE SEVERE AND IRREPARABLE HARM TO YOUR DATA, for which there is no remedy.

Special Note for DBA Classic Customers:  If you are a former DBA Classic customer accustomed to using the old system's database maintenance program, please be aware that DBA Next-Gen's Firebird database is a completely different technology than the Pervasive database used by DBA Classic. Firebird is a single table, relational database that uses automatic triggers and numerous and complicated linkages among fields and tables. If you delete linked records or edit the wrong fields, you can destroy critical data relationships that can't be recovered.