Bug #33746 Error when I insert a registry
Submitted: 8 Jan 2008 17:25 Modified: 8 May 2008 5:51
Reporter: Dayvison Pellegrina Email Updates:
Status: Duplicate Impact on me:
None 
Category:Connector / ODBC Severity:S3 (Non-critical)
Version:3.51.19 and 3.51.21 OS:Windows
Assigned to: CPU Architecture:Any

[8 Jan 2008 17:25] Dayvison Pellegrina 
Description:
Hello People !!!

There is a problema when i insert a registry using the versions *.19 and *.21. When i using the version *.12 i dont have any errors. I think this is a bug of tthis driver version. 

The errors is:

Microsoft OLE DB Provider for ODBC Drivers error '80040e21' 
ODBC driver does not support the requested properties. 

The error occurs when i open the recordset object this form:
rs.Open "table_name", strConnect, 1, 3

The version of my MYSQL base is 5.0.

How to repeat:
The test code:

<% 	
	strConnect = "********************************"
	Set rs = Server.CreateObject("adodb.recordset")
	rs.Open "tabela", strConnect, 1, 3
	rs.AddNew	

	rs("texto") = now()

	rs.Update
	rs.Close
	Set rs = Nothing
%>

Suggested fix:
When i using the version 3.51.12 this error do not occurs. 

Thanks for all.
[11 Jan 2008 19:36] Jess Balint 
Thank you for the bug report. Can you please include the output of:

  SHOW CREATE TABLE tabela;
[11 Apr 2008 17:45] Rogério Araujo Siqueira 
Follows....

show create table teste
CREATE TABLE `teste` (\n  `id` int(11) NOT NULL auto_increment,\n  `texto` varchar(100) default NULL,\n  PRIMARY KEY  (`id`)\n) ENGINE=MyISAM AUTO_INCREMENT=6 DEFAULT CHARSET=utf8

show variables
version  	5.0.41--log

<%
Set conn = Server.CreateObject("ADODB.Connection")

conn.Open("DRIVER={MySQL ODBC 3.51 Driver};SERVER=host;PORT=3306;DATABASE=db;USER=user;PASSWORD=pass;OPTION=3;") 	
'	strConnect = "********************************"
	Set rs = Server.CreateObject("adodb.recordset")
	rs.Open "teste", Conn, 1, 3
	rs.AddNew	

	rs("texto") = now()

	rs.Update
	rs.Close
	Set rs = Nothing

%>
[8 May 2008 5:51] Tonci Grgin 
Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.

Explanation: Hi all. This is a duplicate of Bug#27158 which is fixed in 3.51.24+, see explanation there.