Bug #47071 VB6 Connector 3.51 OK, Connector 5.1 Crashes program
Submitted: 2 Sep 2009 18:24 Modified: 9 Oct 2009 10:04
Reporter: Andy Wood Email Updates:
Status: Duplicate Impact on me:
Category:Connector / ODBC Severity:S1 (Critical)
Version: OS:Microsoft Windows (XP SP3)
Assigned to: CPU Architecture:Any

[2 Sep 2009 18:24] Andy Wood
Your VB6 RDO example works OK with Connector 3.51 but crashes when used with Connector 5.1.

How to repeat:
Using your example from :- 


Run as is with C/3.51 OK

Change to C/5.1. 

In ...
'rs insert
SQL = "select * from my_rdo"
Set rs = cn.OpenResultset(SQL, rdOpenStatic, rdConcurRowVer, rdExecDirect)

The cn.OpenResultSet statement causes the program to crash.
[3 Sep 2009 6:25] Tonci Grgin
Hi Andy and thanks for your report.

I will need complete test case demonstrating this error and an ODBC DM trace file for crash. Please attach them to report.
[3 Sep 2009 7:40] Andy Wood
Trace file using 5.1 connector

Attachment: SQL 5.1.LOG (application/octet-stream, text), 116.21 KiB.

[3 Sep 2009 7:42] Andy Wood
Could not get trace file, this instead

Attachment: Connector 3.51 myodbc.sql (text/plain), 563 bytes.

[3 Sep 2009 7:52] Andy Wood
2 VB6 Projects one for each connector type

Attachment: MySQL Test.rar (application/force-download, text), 3.58 KiB.

[3 Sep 2009 10:34] Tonci Grgin
Sorry Andy.

Both VB6 and RDO are long EOL-ed by MS and I'll probably have to set up separate 32bit VM for your problem. I fear installing VB6 on primary test box which already has VS2005 and 2008 and is W2K8x64 (RDO is exclusively 32bit).

Also, 5.1 trace is cut before any error is raised and before call completes thus this could be some internal problem with VB6 (Project1        1140-12d0	ENTER SQLDescribeCol ).
[3 Sep 2009 10:48] Tonci Grgin
Remote Data Objects (RDO): RDO was designed specifically to access remote ODBC relational data sources, and made it easier to use ODBC without complex application code. It was included with Microsoft Visual Basic versions 4, 5, and 6. RDO version 2.0 was the final version of this technology.
[3 Sep 2009 12:05] Andy Wood
The reason for wanting this looked at is that one of our customers is suffering very badly from bug 39878 using Connector 3.51 and I was hoping that 5.1 would cure it...
[3 Sep 2009 12:13] Tonci Grgin
Andy, I am not sure what we can do about Bug#39878 in c/ODBC. I am also not sure that we can do anything on this too. Mind you, c/ODBC 5.1 is much more strict in obeying ODBC standards than 3.51 is so using it with such oooolllldddd tools is not something I would advise.
[3 Sep 2009 19:52] Andy Wood
I see you have made some movement on 39878!

That would be the preferable route to cure my problems...
[14 Sep 2009 6:22] Tonci Grgin
Jess has brought to my attention that this report is probably a duplicate of Bug#41942. Please retest with latest snapshot before we release c/ODBC 5.1.6 officially.

Thanks Jess.
[14 Sep 2009 7:21] Andy Wood
I do not have the environment to build the snapshot.

Please could you make the windows installer version of this available to me and I will test it immediately.
[9 Oct 2009 10:04] Andy Wood
Please could you tell me where to download a built Windows 5.1.6 ODBC Connector to try?