use odbc 5.0 in vc6-ADO problem.

------=_Part_68546_18481207.1155635976836
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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 EXIT SQLGetConnectAttrW with return code 0
(SQL_SUCCESS)
SQLHDBC 01BD2708
SQLINTEGER 109
SQLPOINTER 0x0013E824
SQLINTEGER 514
SQLINTEGER * 0x00000000

MSDEV fdc-124 ENTER SQLGetInfoW
HDBC 01BD2708
UWORD 26
PTR 0x0013EA24
SWORD 4
SWORD * 0x00000000

MSDEV fdc-124 EXIT SQLGetInfoW with return code 0
(SQL_SUCCESS)
HDBC 01BD2708
UWORD 26
PTR 0x0013EA24 (2)
SWORD 4
SWORD * 0x00000000

MSDEV fdc-124 ENTER SQLAllocStmt
HDBC 01BD2708
HSTMT * 0013EBF4

MSDEV fdc-124 EXIT SQLAllocStmt with return code 0
(SQL_SUCCESS)
HDBC 01BD2708
HSTMT * 0x0013EBF4 ( 0x01bd20d0)

MSDEV fdc-124 ENTER SQLSetStmtAttrW
SQLHSTMT 01BD20D0
SQLINTEGER 18
SQLPOINTER 0x0000000A
SQLINTEGER 0

------=_Part_68546_18481207.1155635976836--

Re: use odbc 5.0 in vc6-ADO problem.

C/ODBC v3 can work with stored procedures under most circumstances. C/ODBC v3
can execute a stored procedure but it cannot report back to the caller any
meta-data about the stored procedure nor can it handle output parameters.
These weaknesses are being addressed in C/ODBC v5.

C/ODBC v5 is an Alpha release which means some features are missing. The
upcoming Beta release will be a feature freeze and focus will turn to bugs,
stability, performance etc.

If you are using C++ and the ODBC CLI in new code then you should find that
you have the flexability to work around these weaknesses in C/ODBC v3 until
C/ODBC v5 becomes Generally Available (GA).

Peter

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc@m.gmane.org