Fixed in Ver 7 Re: Problems with Intersolv ODBC Informix 5 driver!!!

GUESS WHAT.... THE PROBLEM IS IN THE I-NET DRIVER VERSION 5... IT IS FIXED IN I-NET DRIVER VERSION 7.... Sham Vaidya In article <5d5i0t$8jl@lana.zippo.com>, Sham says... > >Hi, > >We have a developer who has been evaluating the Intersolv ODBC driver for >Informix 5 version 2.10. The issue he faces is that the drivers are >retrieving messages from the message queue and dispatching them. That >is they are making Windows API calls > >GetMessage >DispatchMessage > >These functions appear to get called in at least the following functions > >SQLConnect >SQLExecDirect >SQLFetch > >The effect of this could be that any user input, command message or timer >message can interrupt a piece of code that tries to interact with the >database.I am in total disbelief if this is indeed the situation. Typically >systems have ONE central location for interrupt handlers. > >In our test code on a SQLExecDirect the program jumps into the TimerEvent >handler, and if there are several processes running on the PC, the TimerEvent >handler could be invoked multiple times (because of different invoking sources >(SQLConnect, SQLExecDirect or a SQLFetch) this could cause problems sooner >or later!! I wouls also tend to believe that it would affect performance. > >Is this the way the ODBC Driver was designed? Any thoughts/ideas on what's >the issue we are seeing. We have just downloaded the eval copy of version >2.12 and will follow up on this email. > >Any inputs appreciated. I hope Intersolv will comment on this one... > >Thanks > >Sham Vaidya >smvaidya@auto.rockwell.com >