ODBC-INTERSOLV vs. CLI
ps connected to Informix 7.31 via ODBC: the INTERSOLV 3.11 driver worked for linked Access tables but gave wrong count(*) results from Visual Basic, while the CLI 3.31 driver worked in VB but not for Access linked tables. Imran Hussain suggested checking onstat -g ses. Noel Griffin advised adding WorkArounds=64 and WorkArounds2=64 to the DSN registry settings. Outcome not confirmed.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
I am trying to connect thru ODBC to an informix 7.31 server. When I use the INTERSOLV driver (3.11 for informix 9 v 3.11.00.07), it works great when linking tables thru MS Access, but ut returns erroneous counts when performing SQL's with count(*) in them from Visual Basic apps. When I use the CLI driver, VB seems to work great, but I cannot view linked tables in Access. Any ideas here? I am using the CLI 3.31 32-bit drivers (version 3.31.00.10287) Thanks! pstarkey@cinergy.com
Hi,
Do a "onstat -g ses" on the server and see what is being actually sent to
the server. It should not matter what ODBC driver you use, it is the
server that returns the result.
BTW, since you use ODBC, try WinSQL at http://www.imranweb.com/freesoft.
It is free.
Regards
ps wrote:
> I am trying to connect thru ODBC to an informix 7.31 server. When I
> use the INTERSOLV driver (3.11 for informix 9 v 3.11.00.07), it works
> great when linking tables thru MS Access, but ut returns erroneous
> counts when performing SQL's with count(*) in them from Visual Basic
> apps.
>
> When I use the CLI driver, VB seems to work great, but I cannot view
> linked tables in Access. Any ideas here? I am using the CLI 3.31
> 32-bit drivers (version 3.31.00.10287)
>
> Thanks!
> pstarkey@cinergy.com
--
=====================================================================
Imran Hussain
imranh@imranweb.com
For FREE Software visit
http://www.imranweb.com/freesoft
=====================================================================
I remember reading a long time ago about a setting in the Intersolv driver which controlled whether counts from Access where correct or an approximation. Sorry, cannot remember what the setting is (it was a few years ago). -- Bashar Chalabi CTL, London ps <ps@ps.net> wrote in message news:38876b5c.5187939@news.iquest.net... > I am trying to connect thru ODBC to an informix 7.31 server. When I > use the INTERSOLV driver (3.11 for informix 9 v 3.11.00.07), it works > great when linking tables thru MS Access, but ut returns erroneous > counts when performing SQL's with count(*) in them from Visual Basic > apps. > > When I use the CLI driver, VB seems to work great, but I cannot view > linked tables in Access. Any ideas here? I am using the CLI 3.31 > 32-bit drivers (version 3.31.00.10287) > > Thanks! > pstarkey@cinergy.com
Hi Add a key to the HKEY_LOCAL_MACHINE, or HKEY_CURRENT_USER -> Software -> ODBC -> ODBC.INI where your registered ODBC DSN settings shoule be. Add 'WorkArounds' = 64, and 'WorkArounds2' = 64, if you have the InterSolv 3.11 with the 3.11 patch for ADO and Informix DECIMAL Types. Regards NOEL GRIFFIN Ireland Bashar Chalabi <bashar@ctl.com> wrote in message news:jyXh4.87$7R.1014@news.colt.net... > I remember reading a long time ago about a setting in the Intersolv driver > which controlled whether counts from Access where correct or an > approximation. Sorry, cannot remember what the setting is (it was a few > years ago). > > -- > Bashar Chalabi > CTL, London > > > ps <ps@ps.net> wrote in message news:38876b5c.5187939@news.iquest.net... > > I am trying to connect thru ODBC to an informix 7.31 server. When I > > use the INTERSOLV driver (3.11 for informix 9 v 3.11.00.07), it works > > great when linking tables thru MS Access, but ut returns erroneous > > counts when performing SQL's with count(*) in them from Visual Basic > > apps. > > > > When I use the CLI driver, VB seems to work great, but I cannot view > > linked tables in Access. Any ideas here? I am using the CLI 3.31 > > 32-bit drivers (version 3.31.00.10287) > > > > Thanks! > > pstarkey@cinergy.com > >