Hello,
I have also noticed this bug and have already downloaded the binaries in the
tarball and read the readme.txt file.
My questions are:
1. If pgAdminII is already installed do I really need to run regsvr32 on
each file?
2. If regsvr32 needs to be run for each file, just want to confirm that you
mean the (1) .ocx, (12) dll's, and the (1) .exe? (I know the readme says to
do this for each file, but I just want a confirmation before messing with
the registry.)
3. If I need to run regsvr32 on each file from the tarball, will new CLSID
entries be created or will they just be updated with a new version? (Really
don't want to clutter up my registry if it is going to create new entries.)
4. Will this fix also allow the update wizard to correctly identify the most
current odbc driver available as 7.02.0001? (It is now showing the most
current driver as version 7.01.0006.)
Thanks for the information and to Dave for creating, supporting, and
maintaining a great tool!
Regards, Andy.
> Thanks Michael, I've committed a fix (and updated the dev binaries) to CVS
> at http://cvs.pgadmin.org.
>
>Regards, Dave.
>
>> -----Original Message-----
>> From: Michael Moehle [mailto:m.moehle@nikocity.de]
>> Sent: 21 April 2002 11:33
>> To: pgadmin-support@postgresql.org
>> Subject: [pgadmin-support] pgadminII and odbc version 7.02.0001
>>
>>
>> Hello,
>>
>> i think i have found a little bug in
>> pgadminII.
>> With the newest version of the odbc driver.
>> When i try
>> to use the explain in a sql-query pgadmin
>> claims
>> about the wrong odbc driver version
>> (must be higher then 7.01.0006.)
>>
>> greetings
>>
>> M.Moehle
>>
>> MBD-Team Bordesholm
>> Bahnhofstrasse 41
>> 24582 Bordesholm
>> m.moehle@nikocity.de
