RE: mySQL does not support ADO??? - craig salee - com.mysql.lists.win32

5 messages in com.mysql.lists.win32RE: mySQL does not support ADO???

From	Sent On	Attachments
Kelvin Kline	26 Feb 2003 20:43
Serkant Karaca	26 Feb 2003 23:41
Public Folder: MySQL	27 Feb 2003 07:25
craig salee	27 Feb 2003 11:01
jbon...@sola.com.au	27 Feb 2003 14:24

Subject:	RE: mySQL does not support ADO???
From:	craig salee (cra...@rocksaltlabs.com)
Date:	02/27/2003 11:01:16 AM
List:	com.mysql.lists.win32

I was under the impression that MyODBC was not as reliable as OLE? Is this true? If this is true, why are you using MyODBC? The reason I ask, is that I'm about to convert one of my applications that uses MyODBC to OLE and I wanted to make sure I knew of any issues related to OLE.

-----Original Message----- From: craig salee [mailto:crai...@hotmail.com] Sent: Thursday, February 27, 2003 1:51 PM To: in...@rocksaltlabs.com Subject: Fwd: RE: mySQL does not support ADO???

From: "Public Folder: MySQL" To: "Kelvin Kline" , Subject: RE: mySQL does not support ADO??? Date: Thu, 27 Feb 2003 07:25:48 -0800 Try using different connection options in your connection string (or DSN) and try different cursors. Most ADO/MyODBC problems with ADO are related to variable length text fields. MySQL will report then length of a VARCHAR field as being only the length of the longest item stored in it. The field may be longer, but that's not what gets reported. This can usually be solved by using a client-side cursor (or using connection.execute statements.) Some other ADO/MySQL issues can be solved by simply using a client-side cursor or changing the type of recordset you open, but sometimes this can create new problems. I stopped messing around with the various ADO errors I got with MySQL/MyODBC and just started issuing SQL execute statements in my code.

It works great. I have never looked back. Unfortunately, MySQL/MyODBC is not a drop in replacement for MSSQL. It will do the job quite nicely in most cases, but requires some tweaking in your code to make it work. -Kevin

-----Original Message----- From: Kelvin Kline [mailto:kelv...@yahoo.com] Posted At: Wednesday, February 26, 2003 8:44 PM Posted To: MySQL Conversation: mySQL does not support ADO??? Subject: mySQL does not support ADO???

From: To: win...@lists.mysql.com Subject: [mySQL VS6 C++ ADO myODBC Multiple Updates fail]

Description: 1) change a field in an ADO recordset 27Feb03 2) do a recordset->Update() 3) repeat 1 & 2 get this error:

Code = 80040e38 Hex WCode = 3128 Decimal Meaning = IDispatch error #3128 Source = Microsoft Cursor Engine Description = Row cannot be located for updating. Some values may have been changed since it was last read. [p MDAC 2.7 cursor client]

nb If I put multiple recordset->Update() statements immediately after the 1st there is no error. So the problem is because some data (non key) is changed ( double, not varchar data)

How-To-Repeat: repeat steps 1 & 2 above sometimes I can do 2 or 3 change+Update before error see http://www.devshed.com/Server_Side/MySQL/ODBC/comments/9901059

99/1000313305/1000314956/349238212 for people having various Update problems in VB last year Fix: some forums with similar VB problems suggest: "abandon ADO and use SQL commands" This is not a "fix" for ADO. Synopsis: ADO update fails on some iteration Submitter-Id: Originator: C Skinner Organization: RewardTech MySQL support: none Severity: critical Priority: high Category: [mysqld, mysql client, C Class: [ sw-bug | doc-bug | change-request | support ] Release: mysql-3.23.38 Exectutable: [mysqld, mysqld-opt] Environment: Pent3 System: Compiler: VC++ 6.0 Architecture: i

Protect your PC - Click here for McAfee.com VirusScan Online