602SQL Documentation Index  

Accessing 602SQL Data through ODBC

An ODBC driver (version 3.0 ODBC specification) is a part of the basic installation of 602SQL. It supports ODBC programming on level 2 (the highest level).

ODBC is sometimes referred to as a slow and ineffective database interface. This is generally related to the ODBC driver quality. The ODBC driver for 602SQL server adds only a minimal load to the client-server communication and may be used effectively.

Applications are the data sources in 602SQL. If you want to access more applications, create more data sources or do not specify the Application name parameter when creating the data source. You will be prompted to specify the name of the application each time you connect to the server. This may not be used if the connection should be done without user intervention.

The Connection String includes the information needed to connect successfully. You can use the following in C#:

Connect to the 602SQL Server with the data source name test11sql, TEST11 application, as the user X with the password Y:

private static OdbcConnection odbcConn = new OdbcConnection("DSN=test11sql;UID=x;PWD=y;SCHEMA=TEST11");

602SQL ODBC Driver Restrictions

The properties specific for 602SQL are not accessible through ODBC. You may not enter split seconds through ODBC into the TIME and TIMESTAMP types. The TIMESTAMP type in 602SQL does not store split seconds, and the split seconds in the TIME type require SQL syntax that exceed the standard used in the ODBC specification.

It is usually necessary for a table to have a unique index (primary key) to modify data in the table through the ODBC interface.

Do not use inverted commas in the meaning of string delimiters in the SQL routines invoked via the ODBC interface - it will not be possible to translate such routine, since the inverted commas (irrespective of the setting in SQL option SQLOPT_QUOTED_IDENT) are always interpreted as identifier delimitation!

List of topics: