RE: Informix ODBC driver and VB

Thanks to all who replied. Using Sergey's suggestion, I worked with our DBA and found that what was actually passed to Informix by the Intersolv driver was different from the Informix Driver. Intersolv passed "EXECUTE PROCEDURE myquery()" while the Informix driver passed "EXECUTE PROCEDURE myquery" With ADO, since you can just specify the Stored Procedure name and optionally add parameters, it appears that the Informix driver didn't automatically add the parenthesis when no parameters are used. I tried telling VB the stored procedure name was myquery(), but then the driver would return error -951. What finally worked, was to upgrade to Informix 3.32 as bc_foster suggested. While that one still doesn't add the parenthesis, it doesn't fail when I tell VB the name includes them. Not a perfect answer, but it does work. Again, thanks to all, Scott DeLagrange Scott.DeLagrange@CibaVision.Novartis.Com <mailto:Scott.DeLagrange@CibaVision.Novartis.Com> 678-415-3299 -----Original Message----- From: Sergey E. Volkov [SMTP:sve@raiden.bancorp.ru] Sent: Tuesday, October 31, 2000 8:38 AM To: informix-list@iiug.org Subject: Re: Informix ODBC driver and VB 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

Looks like I spoke too soon. While 3.32 did fix my original problem, more showed up. Executing other stored procedures would return error - 956 ( I incorrectly posted -951 earlier) when they execute correctly with the Intersolv driver. I've spent too much time working on this, so for now, I'm sticking with the Intersolv driver. Hopefully Informix will get it right pretty soon. Thanks all who did reply, though. Scott In article <8tp8h8$e8e$1@news.xmission.com>, scott.delagrange@cibavision.Novartis.com wrote: > > Thanks to all who replied. Using Sergey's suggestion, I worked with our DBA > and found that what was actually passed to Informix by the Intersolv driver > was different from the Informix Driver. Intersolv passed "EXECUTE PROCEDURE > myquery()" while the Informix driver passed "EXECUTE PROCEDURE myquery" > With ADO, since you can just specify the Stored Procedure name and > optionally add parameters, it appears that the Informix driver didn't > automatically add the parenthesis when no parameters are used. I tried > telling VB the stored procedure name was myquery(), but then the driver > would return error -951. What finally worked, was to upgrade to Informix > 3.32 as bc_foster suggested. While that one still doesn't add the > parenthesis, it doesn't fail when I tell VB the name includes them. Not a > perfect answer, but it does work. > > Again, thanks to all, > > Scott DeLagrange > Scott.DeLagrange@CibaVision.Novartis.Com > <mailto:Scott.DeLagrange@CibaVision.Novartis.Com> > 678-415-3299 > > -----Original Message----- > From: Sergey E. Volkov [SMTP:sve@raiden.bancorp.ru] > Sent: Tuesday, October 31, 2000 8:38 AM > To: informix-list@iiug.org > Subject: Re: Informix ODBC driver and VB > > 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 > > Sent via Deja.com http://www.deja.com/ Before you buy.