Getting Started






Quick Links








Create a Data Source

Edit a Data Source

Test a Connection

Check the Server

Data Source Type

Data Source Name

Environment Info

Server / Host

ODBC Options

Sample Data Source


Data Source Name

Screen ShotEach data source must be named uniquely and this name should be fairly descriptive.

Note that this name is NOT the same as the physical file name of a Generic or CLOA only data source.

The data source name is used in the following places:

  • In a Generic data source to uniquely identify an individual data source and dictionary. See the Sample Data Source for more details.
  • In the DSEDIT list of existing USER and SYSTEM data sources. See Edit an Existing Data Source.
  • In the connection string of an ODBC application, when using a USER or SYSTEM data source (DSN=datasourcename). See the Omnidex documentation for more details about ODBC connection string arguments. Note that Generic data sources are specified in the connection string by passing the location and file name of the physical dsn file (FILEDSN=c:\omnidex\demo\orders.dsn).
  • In the Microsoft ODBC Data Source Administrator, all Omnidex data sources are visible within this application. However, they can only be edited with DSEDIT.



The data source name:

  • must be unique
  • is limited to 30 characters
  • can contain letters (a - Z) and numbers (0 - 9) and under scores
  • cannot contain blanks



DISC recommends that the name describe something about the environment that it will connect to.
For example, assume the data source will connect to an Oracle data base named Sales located on a Linux server named LX1. The data source name might look something like this:


  • ODX - indicates that this is an Omnidex data source.
  • SALES - this is the name of the data base.
  • LX1 - this is the name of the server.
  • ORA - indicates that the data is in an Oracle database.

Following these naming requirements and recommendations will make choosing which data source to use a much simpler process.