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:datasources [2011/01/12 01:15]
els
dev:odbc:datasources [2016/06/28 22:38] (current)
Line 3: Line 3:
 ====== 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 10: Line 10:
 ===== ODBC Datasources ===== ===== ODBC Datasources =====
  
-The standard ODBC interface uses datasources to connect to an underlying database.+The standard ODBC interface uses datasources to connect to an underlying database.  Datasources provide the connection information to get to the underlying data, and each database vendor must provide their own interface to creating these datasources. ​ Omnidex provides several options for datasources.
  
-[Discuss here]+The Omnidex ODBC Driver supports the standard methods of connecting to the databases - Machine Datasources (SYSTEM and USER Datasources) and File Datasources. ​ The driver supports DSN-less connections as well.
  
-==== Types of Omnidex ​Datasources ====+==== Machine ​Datasources ====
  
-The Omnidex ​ODBC Driver supports ​the standard methods of connecting ​to the databases - Machine Datasources ​(SYSTEM and USER Datasourcesand File Datasources.  ​The driver supports DSN-less connections as well.+The standard ​ODBC interface provides ​the ability ​to create two types of Machine Datasources: System ​Datasources and User Datasources.  ​When creating one of these datasources,​ the ODBC Data Source Administrator provided by Microsoft will automatically launch an Omnidex wizard to prompt you through the creation process. ​ Consult this [[dev:​odbc:​wizard|tutorial]] for instructions about creating datasources using this wizard.
  
 +Once the Machine Datasource has been created, it can be referenced by name in third-party applications that use ODBC.  Consult each third-party applications'​ documentation for instructions about referencing Machine Datasources in their application.
  
-{{page>:dev:odbc:datasources_include&​nofooter&​noeditbtn}}+Machine Datasources can also be referenced in an ODBC call to either SQLConnect or SQLDriverConnect. ​ In the following example, the name of the Machine Datasource is //​simple//​. 
 + 
 +  SQLConnect( hdbc,  
 +              (SQLCHAR*) "​simple", ​  
 +              SQL_NTS, NULL, 0, NULL, 0); 
 + 
 +  SQLDriverConnect( hdbc, NULL,  
 +                    (SQLCHAR*) "​DSN=simple",​  
 +                    SQL_NTS, NULL, 0, NULL, SQL_DRIVER_NOPROMPT);​  
 + 
 + 
 + 
 +==== File Datasources ==== 
 + 
 +The standard ODBC interface provides the ability to create File Datasources. ​ Microsoft'​s ODBC Data Source Administrator will automatically launch an Omnidex wizard to prompt you through the creation process for File Datasources as well.  Consult this [[dev:odbc:​wizard|tutorial]] for instructions about creating datasources using this wizard. 
 + 
 +It is also possible to manually create File Datasources for Linux computers that run a Linux-based ODBC Manager, such as unixODBC. ​ These can be created using a text editor. ​ Consult the [[dev:odbc:filedsn|ODBC File DSN Syntax Specification]] for instruction on manually creating these files. 
 + 
 +Once the File Datasource has been created, it can be referenced in third-party applications using the filename. ​ Consult each third-party applications'​ documentation for instructions about referencing File Datasources in their application. 
 + 
 +File Datasources can also be referenced in a call to SQLDriverConnect. 
 + 
 +  SQLDriverConnect( hdbc, NULL,  
 +                    (SQLCHAR*) "​FILEDSN=simple.dsn",​  
 +                    SQL_NTS, NULL, 0, NULL, SQL_DRIVER_NOPROMPT);​ 
 + 
 + 
 +==== DSN-Less Connection ==== 
 + 
 +Omnidex also allows ODBC applications to connect to an Environment File without the need for a Machine or File Datasource. ​ All of the needed information is found in the connection string. ​ This approach may not be supported by some third-party applications;​ however, it can always be used in custom applications that call SQLDriverConnect. 
 + 
 +  SQLDriverConnect( hdbc, NULL,  
 +                    (SQLCHAR*) "​DRIVER={OMNIDEX};  
 +                                CONNECTIONSTRING=[dbserver:​7555]D:​\\class\\simple.xml",​  
 +                    SQL_NTS, NULL, 0, NULL, SQL_DRIVER_NOPROMPT);​
  
  
 =====  ===== =====  =====
  
-**[[dev:​odbc:​home|Prev]]** | **[[dev:​odbc:​sample|Next]]**+**[[dev:​odbc:​home|Prev]]** | **[[dev:​odbc:​sample_c|Next]]** ​
  
 ====== Additional Resources ====== ====== Additional Resources ======
  
 See also:  See also: 
- +  * [[dev:​odbc:​filedsn|ODBC File DSN Syntax Specification]] ​ 
-{{page>:​dev:see_also:​see_also&​nofooter&​noeditbtn}}+{{page>:​dev:​see_also&​nofooter&​noeditbtn}}
  
 {{page>:​bottom_add&​nofooter&​noeditbtn}} {{page>:​bottom_add&​nofooter&​noeditbtn}}
  
 
Back to top
dev/odbc/datasources.1294794958.txt.gz · Last modified: 2016/06/28 22:38 (external edit)