idle curiosity

[chrisf]

not sure of this should go here or in the access post

i'm linking to mysql backend from access and if you try to create a new record
without a timestamp column you get #deleted showing in the fields even though the record updates

while adding a timestamp column fixes the problem my question is:
why does this fix the problem ? or perhaps - what causes this problem?

-just curious

[vssp]

Sorry friend I am not clear your task Please expline brefly it would helpfull for some other to solve your issue

[chrisf]

The problem is that an error occurrred and was fixed but I don't know
why the solution fixed the problem. Is it something to do with the access DB engine? the myodbc connector (v 3.5)? the phase of the moon?

I know it is not specific to the datafields i had set up because it occurs
with updates to many tables and on many access forms, it shouldn't be network latency (the linux box that mysql is on is in the same room as the windows xp box that the access front end is on).

when you create a new record through an access form that is linked through odbc to mysql you get "#deleted" appearing in the textbox(s) on the forms that are linked to the various columns in the table. The database is correctly updated
with the information though and if you close the form and reopen it, you can see your data is in the table. But if you add a timestamp column to the table you
are updating, ACCESS displays the data correctly when inserting a new record.

While I will certainly use the solution (adding a timestamp column) i do not understand why adding a timestamp column (to which i don't even have an element on the form linked to) causes ACCESS to display the info correctly.

actually the more i think about this the more i suspect it is either something to do with the odbc driver or with MS ACCESS , i probably should have posted this in the access area, oh well....

I have tried playing a little with the options for the myodbc connector but this alone didn't seem to fix the problem. I was just wondering if anyone actually knew why this occurs and why adding a timestamp fixes it
I :confused: hate unanswered questions ...