This shows you the differences between two versions of the page.
|
dev:odbc:filedsn [2011/01/12 18:30] els |
dev:odbc:filedsn [2016/06/28 22:38] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | {{page>:top_add&nofooter&noeditbtn}} | ||
| - | ====== Development: ODBC Interface ====== | ||
| - | |||
| - | [[dev:odbc:home|Overview]] | **[[dev:odbc:datasources|ODBC Datasources]]** | [[dev:odbc:sample|Sample Program]] | ||
| - | |||
| - | ---- | ||
| - | |||
| - | |||
| - | ===== Manually Creating an ODBC File Datasource ===== | ||
| - | |||
| - | Omnidex can use File Datasources to access Omnidex Environments. These can be used on both Microsoft Windows and Linux platforms. These File Datasources can be created using the wizard available from Microsoft's ODBC Data Source Administrator program, or they can be created manually using a text editor. | ||
| - | |||
| - | ==== Syntax ==== | ||
| - | |||
| - | Required syntax: | ||
| - | |||
| - | [ODBC] | ||
| - | Driver=Omnidex | ||
| - | ConnectionString=<connection string> | ||
| - | |||
| - | Optional syntax: | ||
| - | |||
| - | ClientTraceOutput=<ON|OFF|ONCE> | ||
| - | ClientTraceFile=<filename> odxodbc.log | ||
| - | ClientTraceOverwrite=ON | ||
| - | ClientTraceClocks=ON | ||
| - | |||
| - | ==== Discussion ==== | ||
| - | |||
| - | === [ODBC] === | ||
| - | |||
| - | This section heading is required and should always be present at the top of the file. | ||
| - | |||
| - | [ODBC] | ||
| - | |||
| - | === Driver === | ||
| - | |||
| - | The Driver entry is required and should always be set to Omnidex. This will then match the registered name of the Omnidex ODBC Driver. | ||
| - | |||
| - | Driver=Omnidex | ||
| - | |||
| - | === ConnectionString === | ||
| - | |||
| - | The ConnectionString entry is required and should be set to an [[dev:sql:connections:home|Omnidex Connection String]]. | ||
| - | |||
| - | ConnectionString=[server1:7555]c:\class\simple.xml | ||
| - | | ||
| - | === ClientTraceOutput === | ||
| - | |||
| - | The ClientTraceOutput entry is optional and controls whether the Client Trace feature is active. The Client Trace feature produces a log file on the ODBC Client that is useful for debugging. The ClientTraceOutput entry should be set to one of the following: | ||
| - | |||
| - | ^ Setting ^ Description ^ | ||
| - | | ON | Turn on the Client Trace facility | | ||
| - | | OFF | Turn off the Client Trace facility | | ||
| - | | ONCE | Turn on the Client Trace facility for one connection only | | ||
| - | |||
| - | ClientTraceOutput=ON | ||
| - | |||
| - | === ClientTraceFile === | ||
| - | |||
| - | The ClientTraceFile entry is optional and controls where the Client Trace log file will be written. If not specified, the Client Trace log file will be named "ODXODBC.LOG" and will be placed in the current working directory for the client process. | ||
| - | |||
| - | ClientTraceFile=c:\class\myodbc.log | ||
| - | |||
| - | === ClientTraceOverwrite === | ||
| - | |||
| - | The ClientTraceOverwrite entry is optional and controls whether the Client Trace log file will be overwritten. If not specified, the Client Trace log file will not be overwritten. | ||
| - | |||
| - | ClientTraceOverwrite=ON | ||
| - | |||
| - | === ClientTraceClocks === | ||
| - | |||
| - | The ClientTraceClocks entry is optional and controls whether the Client Trace log file will contain timing information. If not specified, the Client Trace log file will not contain timing information. | ||
| - | |||
| - | ClientTraceClocks=ON | ||
| - | |||
| - | ====== Additional Resources ====== | ||
| - | |||
| - | See also: | ||
| - | |||
| - | {{page>:dev:see_also:see_also&nofooter&noeditbtn}} | ||
| - | |||
| - | {{page>:bottom_add&nofooter&noeditbtn}} | ||
| - | |||
| - | ### | ||
| - | |||
| - | ===== ===== | ||
| - | |||
| - | **[[prev|Prev]]** | **[[next|Next]]** | ||
| - | |||
| - | ====== Additional Resources ====== | ||
| - | |||
| - | See also: | ||
| - | |||
| - | {{page>:section:chapter:see_also&nofooter&noeditbtn}} | ||
| - | |||
| - | {{page>:bottom_add&nofooter&noeditbtn}} | ||