bionsmooth.blogg.se

#Odbc manager locatio how to#
#Odbc manager locatio drivers#
#Odbc manager locatio update#
#Odbc manager locatio driver#

I added method 7 to the class, since I don't find any method in the.

public static RegistryKey OpenComplexSubKey(RegistryKey baseKey, string complexKeyStr, bool writable) Įxcept for method 7, the signatures of the above methods are self explanatory.

public static ODBCDSN GetUserDSN(string dsnName).

public static ODBCDSN GetUserDSNList().

public static ODBCDSN GetSystemDSN(string dsnName).

public static ODBCDSN GetSystemDSNList().

public static ODBCDriver GetODBCDriver(string driverName).

public static ODBCDriver GetODBCDrivers().

This ODBCManager class has the following static methods. Apart from the ODBCManager, the DLL has two other classes: ODBCDriver and ODBCDSN. So no instance needs to be created (Infact users can't create one, since the class is following singleton pattern). This class is present in the DLL ODBCMngr.DLL. ODBCManager class is defined in ODBCMngr namespace.

#Odbc manager locatio driver#

But we have to write our own routines to talk to the database using ODBC provided by C++/C# or whatever language we want to use (That supports ODBC Driver API). Now, if we have an Oracle ODBC driver installed in our machine, then we don't need to have the Oracle S/W (Expensive) to talk with that database. For example, let us suppose we have an Oracle database which has some tables in it.

#Odbc manager locatio drivers#

Main use of these drivers is, without having a client program supplied by the vendor of the data base, these drivers allow us to interact with databases. There are drivers available for many databases like Oracle, MS Access, SQL Server, Foxbase etc. About ODBC DriverĪn ODBC driver acts as a “translator” between an application and a database. If we use a user DSN, then we'll have to do some extra work to make sure the DSN gets created when a user new to that machine logs in for the first time. User DSNs are stored in HKEY_CURRENT_USER\Software\ODBC\ODBC.INI.Ĭhoosing which type of DSN to use, depends on how our application works.

ODBC.INI has two other subkeys, ODBC Data Sources that contains a list of all system DSNs, and ODBC FileDSN, which contains the name of the folder where file DSNs are stored ( C:\Program Files\Common Files\ODBC\Data Sources is the default).

HKEY_LOCAL_MACHINE\Software\ODBC\ODBC.INI contains all of the system DSNs stored as separate subkeys.

HKEY_LOCAL_MACHINE\Software\ODBC\ODBCINST.INI contains a list of all ODBC drivers installed on the machine.

Most information about DSNs is stored in the registry. We can use regedit to view/modify user or system DSNs, and Notepad works fine for file DSNs. However, there is nothing magical about editing DSNs. We normally create and administer DSNs through the ODBC Data Source Administrator, found in Control Panel on NT/9x machines, or in Administrative Tools for Win2K machines. System and user DSNs are Windows registry based, while file DSNs are stored in the file system. It is a file that contains all the connection parameters used to connect directly to an ODBC driver. A file DSN, however, is not really a data source. System DSNs and User DSNs differ only in who can access them on the system. There are three types of DSNs system, user and file. But we have to keep in mind that DSNs only describe ODBC connections, not OLEDB connections.

#Odbc manager locatio update#

More importantly, using a DSN means we can change the location of our data by updating the DSN, no update to our application is required.

#Odbc manager locatio how to#

It's a simple and standard way to describe how to connect to a data source (database) using an ODBC driver. I have lifted most of the following stuff from the Internet) About DSNĭSN is an acronym for Data Source Name. (Experienced readers can ignore/skim through this section. Also, this class gives the users all system as well as user DSNs. Through this article, I want to present readers with an ODBCManager class that allows a user to have a list of ODBC drivers installed in his/her system.

Programmers who are using ODBC to connect to any database, and wish to program in C#/.NET.