ODBC drivers with VB 6.0 & ADO
A developer asked whether VB 6 with ADO could work against Informix 7.23, since Informix, Intersolv and OpenLink ODBC drivers all reported unsupported features such as scroll cursors. Replies suggested using the Informix CLI driver from SDK 2.20 rather than Intersolv; OpenLink staff said server-side keyset cursors work if VB's default cache size of 50 is lowered (dynamic cursors fail even against SQL Server), with a fix due in driver v3.2. Others noted the "optional feature not implemented" error is often harmless (the connection still opens) or masks a real cause such as a wrong password, and suggested adding NLB=True to the connection string. No single definitive fix was confirmed by the original poster.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
I am supporting a group that is attempting to implement with MS Visual Basic 6.0 via ADO against Informix 7.23 UC1 (quite a concept). They are having problems with their ODBC drivers indicating that certain functionality (e.g., scroll cursors) is not supported. Has anyone been successful with this combo? Does any mfr.'s ODBC driver work satisfactorily with VB 6 and Informix? Apparently neither Informix's, Intersolve's nor OpenLink's drivers work well enough to proceed with VB implementation.
Download the SDK 2.20 and use the Informix CLI driver (Informix 2.80 32 BIT). This should help to fix things up. If you use the Intersolv drivers, it will not work. While I did not personally get VB w/ADO to connect to Informix, one of the guys I work closely with did. He was actually using Micro$oft Transaction Server and connecting to 7.30TC6, but it _should_ (don't you love when people say that) work with your version. HTH Thomas G. Smith (tsmith@wdn.com) wrote: : I am supporting a group that is attempting to implement with MS Visual : Basic 6.0 via ADO against Informix 7.23 UC1 (quite a concept). They are : having problems with their ODBC drivers indicating that certain : functionality (e.g., scroll cursors) is not supported. Has anyone been : successful with this combo? Does any mfr.'s ODBC driver work : satisfactorily with VB 6 and Informix? Apparently neither Informix's, : Intersolve's nor OpenLink's drivers work well enough to proceed with VB : implementation. -- Rob Wilson rwilson@ntsource.com
I'm just starting to use VB/ODBC and my problem is that I can' t write to my informix database. I can read but not write. It says it';s read only. But, I have full access to the db. Go figure.
In article <37275D5A.ADDA6342@wdn.com>, "Thomas G. Smith" <tsmith@wdn.com> wrote: > I am supporting a group that is attempting to implement with MS Visual > Basic 6.0 via ADO against Informix 7.23 UC1 (quite a concept). They are > having problems with their ODBC drivers indicating that certain > functionality (e.g., scroll cursors) is not supported. Has anyone been > successful with this combo? Does any mfr.'s ODBC driver work > satisfactorily with VB 6 and Informix? Apparently neither Informix's, > Intersolve's nor OpenLink's drivers work well enough to proceed with VB > implementation. > > Thomas, OpenLink's High-Performance ODBC Drivers certainly work with VB 6.0, the only inconvenience with the current release (v3.0) is the fact that when you choose server based cursors with the VB default cache size of 50 things go wrong. If you change this value to 49 or lower you will see that server based cursors of type keyset work fine. Dynamic cursors do not work even when you use VB 6 against the Microsoft provided ODBC Driver for SQL Server (this is becuase the ADO layer does not do dynamic cursors properly). OpenLink is about to release v3.2 (ETA 10 days time) of its high-performance data access driver suite, this comprises a new set of drivers which have code accomodations for the default cache size of 50 when server based cursors are selected. Please let me know how you get on. -- Best Regards, Kingsley Idehen OpenLink Software http://www.openlinksw.com -----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
Thomas, This will be available in version 3.2 of OpenLink's drivers. These drivers should be released to the public within 14 to 21 days. -- Thanks, Edward A. Geddis Technical Support Consultant OpenLink Software http://www.openlinksw.com Making Technology Work for You Thomas G. Smith <tsmith@wdn.com> wrote in message news:37275D5A.ADDA6342@wdn.com... > I am supporting a group that is attempting to implement with MS Visual > Basic 6.0 via ADO against Informix 7.23 UC1 (quite a concept). They are > having problems with their ODBC drivers indicating that certain > functionality (e.g., scroll cursors) is not supported. Has anyone been > successful with this combo? Does any mfr.'s ODBC driver work > satisfactorily with VB 6 and Informix? Apparently neither Informix's, > Intersolve's nor OpenLink's drivers work well enough to proceed with VB > implementation. >
I'm doing it in VB6 with the Intersolv 3.01 (or 3.11) ODBC drivers like this: dim db as ADODB.Connection . set db = New ADODB.Connection db.ConnectionString = "DSN=dsn;" ' uses default login in ODBC setup db.Open "dsn", "", "" if db.Errors.Count <> 0 if db.State <> adStateOpen < emit nasty messages > End If End If What seems to be happening is that ADO gets an "option not implemented" from ODBC, and reports an error. But it's not an option ADO *has* to have, so it opens the connection anyway. In article <37275D5A.ADDA6342@wdn.com>, tsmith@wdn.com says... > >I am supporting a group that is attempting to implement with MS Visual >Basic 6.0 via ADO against Informix 7.23 UC1 (quite a concept). They are >having problems with their ODBC drivers indicating that certain >functionality (e.g., scroll cursors) is not supported. Has anyone been >successful with this combo? Does any mfr.'s ODBC driver work >satisfactorily with VB 6 and Informix? Apparently neither Informix's, >Intersolve's nor OpenLink's drivers work well enough to proceed with VB >implementation. >
Two solutions (or a combination of both): * Add NLB=True to connection string, i.e. Conn.Open "DSN=infx311;DB=database1;UID=userid;Password=password;NLB=True" * Try opening the datasource in a different ADO app (i.e. IIS, link tables in Access, etc.) This sort of snaps it awake. * If all else fails after the above reboot and try it again. In article <7gacr9$f2q$1@news-2.csn.net>, dwight@rudolph.com (Dwight Rudolph Jr) wrote: > I'm doing it in VB6 with the Intersolv 3.01 (or 3.11) ODBC drivers > like this: > > dim db as ADODB.Connection > . > set db = New ADODB.Connection > db.ConnectionString = "DSN=dsn;" ' uses default login in ODBC setup > db.Open "dsn", "", "" > if db.Errors.Count <> 0 > if db.State <> adStateOpen > < emit nasty messages > > End If > End If > > What seems to be happening is that ADO gets an "option not implemented" > from ODBC, and reports an error. But it's not an option ADO *has* to have, > so it opens the connection anyway. > > In article <37275D5A.ADDA6342@wdn.com>, tsmith@wdn.com says... > > > >I am supporting a group that is attempting to implement with MS Visual > >Basic 6.0 via ADO against Informix 7.23 UC1 (quite a concept). They are > >having problems with their ODBC drivers indicating that certain > >functionality (e.g., scroll cursors) is not supported. Has anyone been > >successful with this combo? Does any mfr.'s ODBC driver work > >satisfactorily with VB 6 and Informix? Apparently neither Informix's, > >Intersolve's nor OpenLink's drivers work well enough to proceed with VB > >implementation. > > > > -----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
Dwight Rudolph Jr wrote: > > I'm doing it in VB6 with the Intersolv 3.01 (or 3.11) ODBC drivers > like this: > [ Example deleted ] > What seems to be happening is that ADO gets an "option not implemented" > from ODBC, and reports an error. But it's not an option ADO *has* to have, > so it opens the connection anyway. I suddenly got this error from a VB6 program that connects to IDS 7.30 via DAO 3.51 and Intersolv 3.11 ODBC driver. It turned out that the password for the connection, which was hardcoded into the application, had been changed on the server. In the errors-collection, there was the following hierarchy of errors(n).description: 0: [INTERSOLV][ODBC Informix driver]Optional feature not implemented. 1: [INTERSOLV][ODBC Informix driver][Informix]User's password is not correct for the database server. 2: [INTERSOLV][ODBC Informix driver]Driver's SQLSetConnectAttr failed. I wonder what the "optional feature not implemented" error has to do with the problem. It certainly had me confused for a moment. Regards, Richard -- +--------------------------+------------------------------------------+ | Dr. Richard Spitz | INTERNET: spitz@ana.med.uni-muenchen.de | | EDV-Gruppe Anaesthesie | Tel : +49-89-7095-6110 | | Klinikum Grosshadern | FAX : +49-89-7095-6420 <-- NEW!!! | | 81366 Munich, Germany | GSM : +49-172-8933578 | +--------------------------+------------------------------------------+