FOUND IT! They had a regedit program to do the dirty work:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\PostgreSQL Unicode]
"APILevel"="1"
"ConnectFunctions"="YYN"
"Driver"="C:\\postgresodbcdlls\\psqlodbc35w.dll"
"DriverODBCVer"="03.51"
"FileUsage"="0"
"Setup"="C:\\postgresodbcdlls\\psqlodbc35w.dll"
"SQLLevel"="1"
"UsageCount"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers]
"PostgreSQL Unicode"="Installed"
Just had to have the dlls placed properly and it worked.
On Fri, Nov 20, 2009 at 11:54 AM, Mike Broers
<mbroers@gmail.com> wrote:
I have gone through the archives and seen people who used the 64bit build and people who build the dsns in the 32 bit version of the odbc manager found under syswow64 but neither of those approaches are what I am looking for.
1. i have an existing environment that is windows 2008 64 bit which has the postgres unicode driver installed and working, when i go to odbc manager i see postgres unicode in the drivers list, and the processes which connect to the database using this driver work fine. this is psqlodbc35w.dll, 8.03.02.00.
2. i have tried to use the msi to install 8.03.02.00 on a second fresh windows 2008 64 bit server and i get the same problem everyone else has, the postgres unicode driver doesnt show up in the drivers list. like i said i can get at it using the odbcad32 under syswow64 but after setting that up it still doesnt work properly (complains about a driver/app mismatch, still doesnt show up in 64 bit drivers list). I have tried installing the 64bit drivers but still get errors.
anyone know how i can further investigate the setup on the working server as to duplicate that working configuration on the new server? the person who configured it initially has left the company and cannot be reached to explain. thanks in advance, hopefully this thread might help someone else in this situation down the road.