Re: Most recent driver aborts transaction after one error

Hiroshi Inoue wrote:
> Bart Samwel wrote:
>
>> Hiroshi Inoue wrote:
>>
>>> Bart Samwel wrote:
>>>
>>>>
>>>> 2. I also encountered an access violation while exiting. The call
>>>> stack was not very informative:
>>>>
>>>>      ntdll.dll!_RtlpWaitForCriticalSection@4()  + 0x5b
>>>> ntdll.dll!_RtlEnterCriticalSection@4()  + 0x46
>>>> psqlodbc35w.dll!023a097e()         ntdll.dll!_RtlpFreeDebugInfo@4()
>>>> + 0x57        ntdll.dll!_RtlDeleteCriticalSection@4()  + 0x78  If
>>>> you want me to try this with a debug-compiled psqlodbc35w, just say
>>>> the word!
>>>
>>>
>>>
>>> It looks like a thread is about to Free a Handle while another thread
>>> is wating for the Handle.
>>> OK please send me the mylog output.
>>
>>
>> I've attached two mylogs: in the first, I ordered my debugger to
>> continue after the access violation, in the second, I immediately
>> killed the program at the point of the access violation. If you need
>> more info, let me know.
>>
>
> Thanks.
> Please retry the dll at
> http://www.geocities.jp/inocchichichi/psqlodbc/index.html .
> Check SQLGetInfo with the option SQL_DBMS_NAME or SQL_DBMS_VERSION
> as well.

OK, that fixes both the access violation and the DBMS_NAME and
DBMS_VERSION issues. The DBMS_NAME is now "PostgreSQL", and the version
is 8.1.3, as expected. Thanks for the quick response!

--Bart