MySQL Bugs: #9027: error when insert "Check each status value"

Bug #9027	error when insert "Check each status value"
Submitted:	7 Mar 2005 19:15	Modified:	30 May 2013 9:45
Reporter:	miguel orellana	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / ODBC	Severity:	S2 (Serious)
Version:	3.51	OS:	Windows (win xp)
Assigned to:		CPU Architecture:	Any

Description:
When I try to insert a record in a field "name" with a control adodc in VB6 and I have a record name "miguel" (6 characters) and insert a record with more that 6 characters I have this message "Check each status value" and my field is a varchar(20). I use mysql 4.1.10 an MyOdbc 3.51.11, I don't have this problem in Mysql 3.x

How to repeat:
error code:
adodc1.recordset.field("name")=text1.text
adodc1.Recordset.Update

Suggested fix:
but if I use this code work ok.

Set cnn = New ADODB.Connection
Set rst = New ADODB.Recordset
cnn.CursorLocation = adUseClient
With cnn
.ConnectionString = "driver={MySQL ODBC 3.51 Driver};server=localhost;uid=root;pwd=mypass;database=mydb;connection=adUseClient"
.Open cnn
End With

rst.Open "INSERT INTO `table` (`name`,`fechacrea`) VALUES ('" & Text1.Text & "','" & Date & "')", cnn, adOpenDynamic, adLockOptimistic

cnn.Close

en español seria "compruebe los valores de estado"

I have the same problem. When I check the Recordset.Fields("FieldName").DefinedSize and Recordset.Fields("FieldName").ActualSize, it show me different value then what I created in mysql database.

Examble, if I create a varchar(50) field, it shows me 5 for definedsize and -1 for actualsize. some text field don't have this problem. Please check since it is critical for the development of my system.

This should be re-verified after the fix for Bug #19345 is committed.

Could you please test with latest release 3.51.19. Thanks in advance.

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.