At 09:11 AM 1999-10-06 +0800, you wrote:
>Willy Gielen writes:
>
>Hi Willy and Barry,
>
>Can you both please do a mysqldump from the table(s) you have problems
>with? Also please include the version number of MyODBC and MySQL you
>are using. Please don't take the data away, if possible.
>
>Willy, make sure you have a timestamp column in the table and a
>primary key field. See the MyODBC README, if you haven't read it.
>
>Make sure the timestamp field is type (14).
>
>To both:
>
>If doesn't work:
>
>- Change any date fields to datetime.
>
>If still doesn't work:
>
>- Try changing any 'float' types to 'double'. Might help and you won't
> lose any data.
>
>And doesn't work:
>
>- Change any blobs to text fields.
>
>Still wall ahead:
>
>- Add an auto_increment field to table, if you don't have one.
>
>Regards,
>
>- Jani
>
>Ps. The Access' error messages 'Write conflict' and 'Another user
> has modified the date' or 'table opened by another user' are all
> information less. It simply means that Access doesn't know, if
> such thing has happened and is guessing things.
>
Dear Jani,
Thank you for your help.
Just made another test. I found that I can add/update/delete
the tables entry AFTER I drop the TIMESTAMP field in the
table. It is contrary to the MySQL manual's instruction.
My version of MySQL is 3.22.26a and MyODBC is v2.5
rgds
Barry
