Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
dev:odbc:home [2011/01/12 18:36]
els
dev:odbc:home [2016/06/28 22:38] (current)
Line 4: Line 4:
 ====== Development:​ ODBC Interface ====== ====== Development:​ ODBC Interface ======
  
-**[[dev:​odbc:​home|Overview]]** | [[dev:​odbc:​datasources|ODBC Datasources]] | [[dev:odbc:sample|Sample Program]] ​+**[[dev:​odbc:​home|Overview]]** | [[dev:​odbc:​datasources|ODBC Datasources]] | [[dev:odbc:sample_c|Sample ​C# .NET Console ​Program]] ​| [[dev:​odbc:​sample_net|Sample C# .NET Windows Program]]  
  
 ---- ----
Line 11: Line 12:
 ===== Overview ===== ===== Overview =====
  
-The Omnidex ODBC Driver is a standard-compliant ODBC driver that provides ODBC access to Omnidex Environments. ​ ODBC is most commonly found in a Microsoft Windows environment;​ however, it can also be found on UNIX platforms through available ODBC managers ​such as unixODBC. ​ Omnidex'​s ODBC Driver is available on both Microsoft Windows and Linux operating systems.+The Omnidex ODBC Driver is a standard-compliant ODBC driver that provides ODBC access to Omnidex Environments. ​ ODBC is most commonly found in a Microsoft Windows environment;​ however, it can also be found on UNIX platforms through available ODBC projects ​such as unixODBC. ​ Omnidex'​s ODBC Driver is available on both Microsoft Windows and Linux operating systems.
  
 The Omnidex ODBC Driver allows standardized access to Omnidex Environments from a multitude of third party tools and applications,​ such as Business Objects, Impromptu, MicroStrategy and Informatica. ​ ODBC also provides access to common office tools, such as Microsoft Access, Excel and Word.  Custom applications can also access Omnidex Environments using the standard ODBC API calls.  ​ The Omnidex ODBC Driver allows standardized access to Omnidex Environments from a multitude of third party tools and applications,​ such as Business Objects, Impromptu, MicroStrategy and Informatica. ​ ODBC also provides access to common office tools, such as Microsoft Access, Excel and Word.  Custom applications can also access Omnidex Environments using the standard ODBC API calls.  ​
  
-The Omnidex ODBC Driver is based on the Version 2.0 of the ODBC standard.  ​+The Omnidex ODBC Driver is based on the Version 2.0 of the ODBC standard.  ​If you are using Version 3.5 of the ODBC standard, calls will automatically be downgraded to Version 2.0.
  
  
 ===== Integrating Omnidex with Third-Party Applications ===== ===== Integrating Omnidex with Third-Party Applications =====
  
-The Omnidex ODBC Driver allows easy integration with many third-party applications. ​ Integration is usually as simple as providing the third-party application with an appropriate [[dev:sql:​connections:​home|connection string]] to point to the existing Omnidex Environment.+The Omnidex ODBC Driver allows easy integration with many third-party applications. ​ Integration is usually as simple as providing the third-party application with an appropriate [[dev:​connections:​home|connection string]] to point to the existing Omnidex Environment.
  
 Omnidex automatically optimizes SQL statements to provide the best performance. ​ Nonetheless,​ there are times when the wording and structure of a SQL statement can affect performance. ​ Each third-party application will use its own method of wording and structuring the SQL statement, and not all approaches generate the best performance.  ​ Omnidex automatically optimizes SQL statements to provide the best performance. ​ Nonetheless,​ there are times when the wording and structure of a SQL statement can affect performance. ​ Each third-party application will use its own method of wording and structuring the SQL statement, and not all approaches generate the best performance.  ​
  
-Some tools allow configuration options that alter the wording or structure that they use.  If you find that you are not obtaining satisfactory performance,​ you may be able to use these configuration options to improve the wording of the SQL statement, and therefore improve the performance.+Some tools allow configuration options that alter the wording or structure ​of the SQL that they use.  If you find that you are not obtaining satisfactory performance,​ you may be able to use these configuration options to improve the wording of the SQL statement, and therefore improve the performance.
  
 Omnidex is often used with third-party packages, but Omnidex is not regularly tested with each and every third-party package. ​ If you have difficulty integrating Omnidex with a particular third-party package, please contact [[appendix:​contactus|Technical Support]]. Omnidex is often used with third-party packages, but Omnidex is not regularly tested with each and every third-party package. ​ If you have difficulty integrating Omnidex with a particular third-party package, please contact [[appendix:​contactus|Technical Support]].
- 
-===== Integrating Omnidex with Custom Applications ===== 
- 
-Custom applications can also call the ODBC API directly for standardized access to Omnidex Environments. Refer to the [[dev:​odbc:​sample|sample ODBC program]] to see an example of a basic application. ​ Developers should be aware that the Omnidex ODBC Driver is based on Version 2.0 of the ODBC standard. 
- 
-An ODBC application must begin by obtaining a handle for the environment and then a handle for the database connection. Memory is allocated for these handles and the information they store. A statement handle, used for processing SQL statements, will be obtained later in the application. Every subsequent CLI call will be passed one of these three handles. 
- 
-The environment handle must be the first handle established. It refers to the data object that contains global information about the current state of the application. The program allocates this handle by calling the SQLAllocEnv() CLI function call. Only one environment handle can be allocated per application,​ and it must be allocated before connection handles can be allocated. 
- 
-The connection handle must be established after the environment handle, but prior to any other CLI function calls. It refers to a data object that contains information associated with a database connection. This data object includes general status information and diagnostic information. The program allocates each connection handle by calling the SQLAllocConnect() CLI function call, and must allocate a connection handle for each connection it makes to a database server. These connection handles are then used to establish database connections and allocate SQL statement handles for use within those connections. 
- 
-The statement handles refers to a data object that contains information about an SQL statement. This data object includes information such as the SQL statement text, any dynamic SQL statement arguments, cursor information,​ bindings for dynamic SQL statement arguments and columns, result values, and status information. A program allocates a statement handle by calling the SQLAllocStmt() CLI function call; a statement handle must be allocated for an SQL statement before that SQL statement can be executed. Also, each allocated statement handle must be associated with a specific database connection handle. The maximum number of statement handles that can be allocated at any one time is limited only by the amount of available system resources (usually stack space). 
- 
  
 =====  ===== =====  =====
  
-**[[dev:​odbc:​sample|Next]]**+**[[dev:​odbc:​datasources|Next]]**
  
 ====== Additional Resources ====== ====== Additional Resources ======
 
Back to top
dev/odbc/home.1294857392.txt.gz · Last modified: 2016/06/28 22:38 (external edit)