Hello!
Does anyone have any clue as to what all the possible return codes are for the ODBC plugin? I can't find this documented anywhere. The code itself, just returns the error #, and it doesn't appear to have any or all of the possible return codes listed anywhere.
[Update]
Also, When I add a system DSN, half the properties end up containing invalid values, or not the ones I specified. Even the Description, and Username get populated incorrectly.
Does anyone else have issues with the nsODBC.dll? or are these problems part of the PostgreSQL ODBC 3.0 driver?
Cheers,
ZimSMS
nsODBC.dll Return Codes
6 posts
Ok , so absolutely no one responded, that's disappointing. 🙁
Has anyone tried to set up Cygwin and PostgreSQL 7.4.2 via NSIS?
I have the PostgreSQL ODBC Driver working, I had to add registry values via the writereg* functions, since the nsODBC.dll failed to add the value pairs with the specified values.
Has anyone tried to set up Cygwin and PostgreSQL 7.4.2 via NSIS?
I have the PostgreSQL ODBC Driver working, I had to add registry values via the writereg* functions, since the nsODBC.dll failed to add the value pairs with the specified values.
Why not contact the plug-in author? Is there no source code available?
Yes, there is source. And it hasn't been updated since October of 2003. The website is in a language that I don't know.
* Module Name: nsODBC.cpp
* Abstract: NSIS ODBC managment plugin
* Author: Vyacheslav I. Levtchenko
* (mail-to: sl@r-tt.com, sl@eltrast.ru)
* Revision History: 20.10.2003 started
* Module Name: nsODBC.cpp
* Abstract: NSIS ODBC managment plugin
* Author: Vyacheslav I. Levtchenko
* (mail-to: sl@r-tt.com, sl@eltrast.ru)
* Revision History: 20.10.2003 started
if its only about setting up the odbc settings in the system panel you don't need a Plugin. You can use the registry. The Information are stored under HKLM\SOFTWARE\ODBC\ODBC.INI.
Once you've set it up you can export the registry key(s) and install them using WriteRegStr/WriteRegDWORD in a modified / unmodified way. In my company it works great with the MS SQL Server, as the neccessary files are already installed.
Once you've set it up you can export the registry key(s) and install them using WriteRegStr/WriteRegDWORD in a modified / unmodified way. In my company it works great with the MS SQL Server, as the neccessary files are already installed.
Has the registry location changed for registering/adding ODBC drivers to Windows 2003 Advanced Server? Can anyone else confirm this?