MySQL Bugs: #62490: #Deleted in Access front end after INSERT

Bug #62490	#Deleted in Access front end after INSERT
Submitted:	21 Sep 2011 10:18	Modified:	28 May 2013 14:12
Reporter:	Ivo Ulrich	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / ODBC	Severity:	S3 (Non-critical)
Version:	5.01.05.00	OS:	Windows (XP SP3)
Assigned to:		CPU Architecture:	Any
Tags:	#DELETED, access

Description:
I am using:

Access 2003 SP3 (Microsoft Jet Engine 4.0.9511.0)
MySQL-Client-Version: 5.0.32
Server Version: 5.0.67
and MySQL ODBC 5.01.05.00 Driver

When I INSERT into linked tables and specifically set a field to NULL in a bound Access Form Access looses track and shows #DELETED# altough the insert was successfull. It is the same problem as described in Bug #10910, I just dont know if it is possible to set FLAG_AUTO_IS_NULL = 8388608 through the Connector/ODBC connection screen.

Thanks

How to repeat:
INSERT into linked mysql table via bound form and 
set a field to NULL before insert (txt_field.Value = Null)

Access looses track and form shows #DELETED# altough the insert was successfull

Could you please provide the result of show create table table_name. Thanks.

CREATE TABLE `investor` (
 `INV_ID` int(11) NOT NULL auto_increment,
 `ANR_ID` tinyint(1) unsigned NOT NULL default '1',
 `KOM_ID` tinyint(1) unsigned NOT NULL default '3',
 `INV_Titel` varchar(50) collate latin1_german1_ci default NULL,
 `INV_Vorname` varchar(50) collate latin1_german1_ci NOT NULL,
 `INV_Nachname` varchar(50) collate latin1_german1_ci NOT NULL,
 `INV_Firma` varchar(150) collate latin1_german1_ci default NULL,
 `INV_Strasse` varchar(50) collate latin1_german1_ci default NULL,
 `INV_Ort` varchar(50) collate latin1_german1_ci default NULL,
 `INV_PLZ` varchar(50) collate latin1_german1_ci default NULL,
 `INV_Post_Adressat` varchar(100) collate latin1_german1_ci default NULL,
 `INV_Post_Strasse` varchar(50) collate latin1_german1_ci default NULL,
 `INV_Post_Ort` varchar(50) collate latin1_german1_ci default NULL,
 `INV_Post_PLZ` varchar(50) collate latin1_german1_ci default NULL,
 `INV_Telefon` varchar(50) collate latin1_german1_ci default NULL,
 `INV_Email` varchar(50) collate latin1_german1_ci default NULL,
 `INV_Beruf` varchar(50) collate latin1_german1_ci default NULL,
 `INV_FN_SZ` varchar(10) collate latin1_german1_ci default NULL,
 `INV_Finanzamt` varchar(50) collate latin1_german1_ci default NULL,
 `INV_StNr` varchar(11) collate latin1_german1_ci default NULL,
 `INV_Passwort` varchar(50) collate latin1_german1_ci default NULL,
 `CRM_USER_ID` tinyint(3) unsigned default NULL,
 `INV_Username` varchar(50) collate latin1_german1_ci default NULL,
 `INV_Aktiv` tinyint(1) NOT NULL default '1',
 `INV_Login_Last` datetime default NULL,
 `INV_Login_Count` int(10) unsigned NOT NULL default '0',
 `lastUpdated` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,
 PRIMARY KEY  (`INV_ID`),
 UNIQUE KEY `INV_Username` (`INV_Username`),
 KEY `CRM_USER_ID` (`CRM_USER_ID`),
 KEY `ANR_ID` (`ANR_ID`),
 KEY `KOM_ID` (`KOM_ID`)
) ENGINE=InnoDB AUTO_INCREMENT=957 DEFAULT CHARSET=latin1 COLLATE=latin1_german1_ci

I couldn't repeat with 5.01.08 please try latest driver if you continue with the issue please attach a screen-shot showing the form with data inserted to try the same values on my side. Thanks.

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.