MySQL Bugs: #8518: connecting in borland c++

Bug #8518	connecting in borland c++
Submitted:	15 Feb 2005 14:48	Modified:	30 May 2013 9:53
Reporter:	Martoh Ngigz	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / ODBC	Severity:	S3 (Non-critical)
Version:	Myodbc 3.51	OS:	Microsoft Windows (windows)
Assigned to:		CPU Architecture:	Any

Description:
am conneting to mysql server on a borland c++ builder6, am using MDAC 2.7 and myodbc 3.51 drivers. Each time I need to open a recordset I have to do it twice. The first time it raises an exemption that I have to catch and try again for it to work. This is how my code looks like:
.
.
.
        TADODataSet * rstSysCode2 = new TADODataSet(this);
        //AssetMgtCtrl::MainCon is a static variable opened at some other place
        rstSysCode2->Connection = AssetMgtCtrl::MainCon;               
        TField * fldAcc;
        rstSysCode->CommandText = "SELECT myVal Main.ValList WHERE SysCode REGEXP '^" & strCode & "-[0-9]+$'";
        try{
              //This part always raises an exeption
                rstSysCode->Open();
        }catch(...){
                try{
                        //second trial works well
                        rstSysCode->Open();
                        if (! rstSysCode->IsEmpty()){
                                fldAcc =  rstSysCode->FindField("myVal");
                                if (fldAcc->IsNull){
                                        rstSysCode2->CommandText = "";
                                }else{
                                        strSysCode = fldAcc->AsString;
                                }
                        }else{

                        }
                }catch(...){

                }
        }

Prior versions to 3.51 of MYODBC dont have this problem but they lack functionality.

How to repeat:
well...I've no Idea.

Suggested fix:
you need to tell me

What exactly the version are you using 3.51.11-1 ?. Because some
bug fixes were introduced that affected the client's connection.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

I'm closing this bug because I can not continue without feedback from the reporter. If you have new info, please reopen the report.