By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,827 Members | 2,220 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,827 IT Pros & Developers. It's quick & easy.

Writing conflict when record is unchanged

P: n/a
Hi all,

In the past few weeks, I've been struggling with setting up an Access
(XP) user interface to a MySQL database. So far, I seem to have been
able to overcome most of the difficulties, but I'm still stuck with
those famous writing conflicts one gets when coupling Access and MySQL.

I've made a simple test case: a small table containing the following
fields:

ID (int, auto_increment, primary key)
Text (varchar 50)
YesNo (bool, default 0)
Timestamp (timestamp, default current_timestamp)

ID and Timestamp should make Access happy, Text and YesNo are the
actual data. MyODBC is set up correctly (I've read all the FAQs afaik).

Now I link the table into Access and create a form with a text box for
the field Text and a checkbox for YesNo. I open the form.

When I change a record, everything's fine. However, when I e.g. click a
checkbox *twice*, so that in the end nothing's changed, and then go to
the next record, a writing conflict pops up. Of course, who cares ---
nothing's changed to the record --- but it's an annoying thing, and
certainly not very user-friendly!

Is there anyone familiar with this problem? Is there a solution? Have I
done something wrong, or is this just an unsolvable Access quirk? (I
know, Access is not the best way to go for a MySQL UI, but Webbased
takes a huge amount of time and isn't as user-friendly; custom app
development is way too expensive).

Thanks for your time!

Yours sincerely,
Onno

Jul 24 '06 #1
Share this Question
Share on Google+
3 Replies


P: n/a
Hi Onno,

THe writeconflict issues between Access and most sql servers is a known
issue. I have had to deal with it myself. One thing you can try is to
make sure that the tables in the sql server (mysql server) all have
default values like '' for text, 0 for numeric and for date values don't
allow any null values (meaning - all date fields must contain data).
This seems to eliminate the writeconflict issue. This means first you
have to update your table(s) and set all nulls to 0 or '' per data type
or assign some default date value for date fields (default date value
like 1/1/1900). Then you can alter your tables and set the default
values of the fields.
Rich

*** Sent via Developersdex http://www.developersdex.com ***
Jul 24 '06 #2

P: n/a
Onno,
I experienced similar problems when linking to Postgres
tables. Because digital machines often have trouble representing the
values of real numbers, you may have to watch the precision of your
table fields that are typed as singles. That is to say use the same
number of decimal places in the code and tables.

Hank Reed
Rich P wrote:
Hi Onno,

THe writeconflict issues between Access and most sql servers is a known
issue. I have had to deal with it myself. One thing you can try is to
make sure that the tables in the sql server (mysql server) all have
default values like '' for text, 0 for numeric and for date values don't
allow any null values (meaning - all date fields must contain data).
This seems to eliminate the writeconflict issue. This means first you
have to update your table(s) and set all nulls to 0 or '' per data type
or assign some default date value for date fields (default date value
like 1/1/1900). Then you can alter your tables and set the default
values of the fields.
Rich

*** Sent via Developersdex http://www.developersdex.com ***
Jul 24 '06 #3

P: n/a
Hi Rich & Hank,

Thank you very much for your replies. My tables do not contain any
float numbers, so that's not the problem, but I think I will give it a
try to remove all NULL values and change them to 0 and empty strings
instead... Perhaps that will help.

Yours sincerely,

Onno

Jul 26 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.