MySQL Bugs: #19429: Recurrence of locking problems after 4.1.14

Bug #19429	Recurrence of locking problems after 4.1.14
Submitted:	28 Apr 2006 21:32	Modified:	29 May 2013 6:20
Reporter:	Eric Wolgemuth	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / ODBC	Severity:	S1 (Critical)
Version:	4.1.18 and 5.0	OS:	Windows (Windows XP)
Assigned to:		CPU Architecture:	Any

Description:
I've been using MySQL as a backend for my access app.  I had various and sundry locking "the record cannot be updated because another user has blah blah blah" that I knocked out using the suggestions here:

*  Timestamp field added to all tables
*  "Return Matching Rows" flag enabled in ODBC
*  No single floats

Unfortunately, I am volunteering at an organization where I wowed them with my original program.  I downloaded 4.1.18 and *poof* all the problems came back.  When I try to edit an existing related record and then return to the main/master record I get the "record cannot be updated..."

I tried download 5.0 and it's still broke.

I tried deleting all my existing data and starting w/fresh data, in case my data was goofy.

I'm sitting here, looking stupid and feeling *very* very frusted

How to repeat:
Create a master form with demographic data:  Name, Address blah blah
Create a detail record showing donations:  date, amount blah blah

edit text field on donation record, return to the master record and get the msg "this record has been changed by another user...."

I'm hosed

Hi Eric. Thanks for your problem report. In order to help you I will need a dump with table structures and some example data showing this problem. I will also like to know ACCESS version and MyODBC version as well as other relevant data you can provide (SP, Access forms etc...).

Hi. It seems that it's related to MS jet update. Please see http://bugs.mysql.com/bug.php?id=15277.

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.