ODBC Error - Multiple-step operaion
Posted: 27.08.2008, 10:07
Hi,
On few configuration, tested Win2003 and WinXP pro
with Zeos 6.6.3 and 6.1.5 with MySQL server.
MyODBC 3.51, got
ODBC Error 0x80040E21 - Multiple-step operation
generated errors. Check each status value.
The table stucture is very simple
Problem table
------------------
CREATE TABLE `shwtype` (
`sho_show_dt` date DEFAULT NULL,
`sho_location_cd` varchar(10) DEFAULT '0',
`sho_show_id` varchar(10) DEFAULT NULL,
`sho_tkt_type` varchar(50) DEFAULT NULL,
`sho_tkt_type_2` varchar(50) DEFAULT NULL,
`sho_price` decimal(10,2) DEFAULT NULL,
`sho_sort_ivr` int(2) DEFAULT NULL,
KEY `LocationShow` (`sho_location_cd`,`sho_show_id`),
KEY `Show_Dt` (`sho_show_dt`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
No problem table
-------------------
CREATE TABLE `shwlmap` (
`sho_location_cd` char(16) NOT NULL DEFAULT '0',
`shw_loc_seq` char(16) NOT NULL DEFAULT '',
PRIMARY KEY (`sho_location_cd`,`shw_loc_seq`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
What could be the problem?
Same table do not have prorblem with MySQL ODBC 5.1,
libMySQL??.dll.
Regards,
KL Chin
On few configuration, tested Win2003 and WinXP pro
with Zeos 6.6.3 and 6.1.5 with MySQL server.
MyODBC 3.51, got
ODBC Error 0x80040E21 - Multiple-step operation
generated errors. Check each status value.
The table stucture is very simple
Problem table
------------------
CREATE TABLE `shwtype` (
`sho_show_dt` date DEFAULT NULL,
`sho_location_cd` varchar(10) DEFAULT '0',
`sho_show_id` varchar(10) DEFAULT NULL,
`sho_tkt_type` varchar(50) DEFAULT NULL,
`sho_tkt_type_2` varchar(50) DEFAULT NULL,
`sho_price` decimal(10,2) DEFAULT NULL,
`sho_sort_ivr` int(2) DEFAULT NULL,
KEY `LocationShow` (`sho_location_cd`,`sho_show_id`),
KEY `Show_Dt` (`sho_show_dt`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
No problem table
-------------------
CREATE TABLE `shwlmap` (
`sho_location_cd` char(16) NOT NULL DEFAULT '0',
`shw_loc_seq` char(16) NOT NULL DEFAULT '',
PRIMARY KEY (`sho_location_cd`,`shw_loc_seq`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
What could be the problem?
Same table do not have prorblem with MySQL ODBC 5.1,
libMySQL??.dll.
Regards,
KL Chin