Informix ODBC driver and VB

We have several custom VB apps developed by a system integrator that connect to our informix DB via an ODBC driver. The DSN was originally configured using the Intersolv 3.01 ODBC driver. We recently upgraded to SDK 2.40 which includes the informix 3.31 ODBC driver. Now, the VB apps, which use ADO, fail whenever they try to execute a stored procedure when no parameters are passed. If the SP requires params and you pass them in, everything works fine. Then error received is -2147217900 which is described as a syntax error. The same exact code works fine with the intersolv driver. The system integrators first response was, "If it works with Intersolv and not with Informix, there must be a bug in the informix one" Has anyone come across this? Are there any known issues with the 3.31 driver? Scott DeLagrange Scott.DeLagrange@CibaVision.Novartis.Com <mailto:Scott.DeLagrange@CibaVision.Novartis.Com> 678-415-3299

Try to look, what statement VB sends to Informix. Use onstat -g sql session_num; I has tried to do too as you with SQL Explorer ( from BCB-4 ) and I did not have any problems. I used Informix ODBC 3.31. Good luck. Sergey. <scott.delagrange@cibavision.Novartis.com> ''''' ' ''''''''':8tmgqj$hj4$1@news.xmission.com... > > We have several custom VB apps developed by a system integrator that connect > to our informix DB via an ODBC driver. The DSN was originally configured > using the Intersolv 3.01 ODBC driver. We recently upgraded to SDK 2.40 > which includes the informix 3.31 ODBC driver. Now, the VB apps, which use > ADO, fail whenever they try to execute a stored procedure when no parameters > are passed. If the SP requires params and you pass them in, everything > works fine. Then error received is -2147217900 which is described as a > syntax error. The same exact code works fine with the intersolv driver. > The system integrators first response was, "If it works with Intersolv and > not with Informix, there must be a bug in the informix one" Has anyone come > across this? Are there any known issues with the 3.31 driver? > > > Scott DeLagrange > Scott.DeLagrange@CibaVision.Novartis.Com > <mailto:Scott.DeLagrange@CibaVision.Novartis.Com> > 678-415-3299

We also have VB apps that use ADO and we experienced some problems with the Informix 3.31 Driver (SDK 2.40) We have upgraded to CLI SDK 2.50.TC2, which include Informix 3.32 32 Bit driver. This appears to have solved our problems, although we don't use stored procedures, I recommend the upgrade. Can be had for free from Intraware http://www.intraware.com Regards Kelly scott.delagrange@cibavision.Novartis.com wrote: > > We have several custom VB apps developed by a system integrator that connect > to our informix DB via an ODBC driver. The DSN was originally configured > using the Intersolv 3.01 ODBC driver. We recently upgraded to SDK 2.40 > which includes the informix 3.31 ODBC driver. Now, the VB apps, which use > ADO, fail whenever they try to execute a stored procedure when no parameters > are passed. If the SP requires params and you pass them in, everything > works fine. Then error received is -2147217900 which is described as a > syntax error. The same exact code works fine with the intersolv driver. > The system integrators first response was, "If it works with Intersolv and > not with Informix, there must be a bug in the informix one" Has anyone come > across this? Are there any known issues with the 3.31 driver? > > Scott DeLagrange > Scott.DeLagrange@CibaVision.Novartis.Com > <mailto:Scott.DeLagrange@CibaVision.Novartis.Com> > 678-415-3299

Version 3.31 has a few of major problems that I have come accross: * the use of aggregate functions in a select statement often requires an explicit cast to avoid errors * Outer Joins sometimes return nothing when one of the selected columns has null values * Select For Update has the 'For Update' portion stripped out when passed through this driver. I think version 3.32 fixes all of these but has produced som new problems. -Brian Sent via Deja.com http://www.deja.com/ Before you buy.