This article will discuss how developers can install custom ODBC drivers to ensure that your applications drivers are not being overwritten.When an application is deployed with ODBC on Windows, the ODBC driver must be installed into the Windows operating system.
Odbc Without Admin Rights Windows Drivers To Ensure![]() The alternative is to create a connection string without using a DSN but instead using the installed driver name. A developer must consider the fact that other applications may also be using their own installations of SQL Anywhere on the same machine, without the end user knowing about it. Odbc Without Admin Rights Windows How To Prevent YourAs such, you have to consider how to prevent your SQL Anywhere components from being updated or replaced by another third-party application, outside of your control. The next time your application runs, the user could encounter problems that will be difficult to track down. Similarly, the installation of your program may overwrite an existing ODBC driver, potentially causing problems with other applications already installed on the machine. Worse, uninstalling another application may remove the ODBC driver that your application relies on, stopping your application before it can even start. This way, you can ensure the location and specifics of the ODBC driver libraries that you want your application to use during normal operation, and you can ensure you will not affect the ODBC drivers of any other applications on the system if your application is updated or uninstalled. Once you understand how this works, you can use the windows API functions to open and write the specific keys you require to automate the process. ![]() Open HKEYLOCALMACHINESoftwareODBCODBCINST.INIODBC Drivers and add a new string value to this key. The name of the string value should be the name of the new driver you are creating. The first tells the ODBC Administrator where to find the setup information used when a new DSN is created; the second tells the ODBC Administrator where to find the ODBC driver when an application refers to it in its connect string. To do this, add a new key to HKEYLOCALMACHINESoftwareODBCODBCINST.INI with the same name as the previous key you createdin your case, CustomDriver. This key will need two string values created for it, one called Driver, and the other called Setup. The values for these strings should be the name and location of the ODBC driver you are planning to use for your application. If you run the ODBC Data Source Administrator application (odbcad32.exe), you will see your new driver included in the list of drivers when you add a new data source.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |