Mailing List
Home
Forum Home
MySQL General - General MySQL discussion
MySQL++ - Programming with the C++ API to MySQL
MaxDB - Everything about MaxDB, formerly known as SAP DB
ODBC - ODBC with the MySQL Connector/ODBC driver
MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP
Java Help - Mostly related to the MySQL Connector/J driver
Perl - Perl support for MySQL with DBI and DBD::mysql
GUI - MySQL GUI Tools
Announcement
Subjects
• mysql openssl Question
• mysql:it 's a db not a dbms how it 's possible?!
• Does the binary log enabling affect the MySQL performances?
• Strange behavior, Table Level Permission
• FULLTEXT query format question
• Preventing Duplicate Entries
• Comparing and writing out BLOBS
• Executing MySQL Commands From Within C Program
• Can 't access mysql after kernel upgrade
• Mysql 4 0 Oracle Stored Procedure Trigger Conversion
• Downgrade Mysql from 4 to 3 23
• MySQL Cluster Software
• mysql test 4 1 fails with the gis test
• ERROR 2002: Can 't connect to local MySQL server through socket
• Getting Identity after INSERT
• Update one field with more fields from another table
• ERROR 1045: Access denied for user: 'root@localhost ' (Using
password: NO)
• mysql have same function mthod as Oracle decode()
 
use odbc 5.0 in vc6-ADO problem.

use odbc 5.0 in vc6-ADO problem.

2006-08-15       - By Yoke

 Back
Reply:     1     2  

Hi all !
I'm use myodbc 3.5.1 first.
It is work good when i have not use store produce.
I used store produce, but it can't explain the syntax, so I installed
myodbcv5.0.

The problem happen, when i test the datasource config.
The prompt is success. But I can't connect with windows ODBC API in
c++.
I use ADO can't connected too.
When i use the compent that VC++ 6 provide MS ADO Data control 6.0(sp6)
and
MS datagrid control 6.0(sp6), the VC6 IDE crash. the connect string is
"Provider=MSDASQL.1;Persist Security Info=False;User ID=root;Data
Source=TMYSQL".

why? is myodbc 3.x can not explain store produce syntax?
And how can use 3.5.x in c++ ? is a myodbc 5.x bug?
thanks.

WinXP sp2
VC ++ 6 sp6
ADO 2

The last odbc trace log :

MSDEV           fdc-124 (See http://fdc-124.ora-code.com) EXIT  SQLGetConnectAttrW  with return code 0
(SQL_SUCCESS)
               SQLHDBC             01BD2708
               SQLINTEGER                 109 <SQL_ATTR_CURRENT_CATALOG>
               SQLPOINTER         0x0013E824
               SQLINTEGER                 514
               SQLINTEGER *        0x00000000

MSDEV           fdc-124 (See http://fdc-124.ora-code.com) ENTER SQLGetInfoW
               HDBC                01BD2708
               UWORD                       26 <SQL_DEFAULT_TXN_ISOLATION>
               PTR                 0x0013EA24
               SWORD                        4
               SWORD *             0x00000000

MSDEV           fdc-124 (See http://fdc-124.ora-code.com) EXIT  SQLGetInfoW  with return code 0
(SQL_SUCCESS)
               HDBC                01BD2708
               UWORD                       26 <SQL_DEFAULT_TXN_ISOLATION>
               PTR                 0x0013EA24 (2)
               SWORD                        4
               SWORD *             0x00000000

MSDEV           fdc-124 (See http://fdc-124.ora-code.com) ENTER SQLAllocStmt
               HDBC                01BD2708
               HSTMT *             0013EBF4

MSDEV           fdc-124 (See http://fdc-124.ora-code.com) EXIT  SQLAllocStmt  with return code 0
(SQL_SUCCESS)
               HDBC                01BD2708
               HSTMT *             0x0013EBF4 ( 0x01bd20d0)

MSDEV           fdc-124 (See http://fdc-124.ora-code.com) ENTER SQLSetStmtAttrW
               SQLHSTMT            01BD20D0
               SQLINTEGER                  18 <SQL_ATTR_PARAM_BIND_TYPE>
               SQLPOINTER          0x0000000A
               SQLINTEGER                   0