MySQL and Microsoft Access...#DELETED???

[tisource]

Interestingly enough, I cannot find much info on this subject.

I have a linux server running MySQL 4.0.12. I have a user accessing this database via ODBC (MyODBY), via Microsoft Access. The wierd thing is that he can write to the table(s) with Access, and he can extract data into Excel, but when he is viewing records in Access, he gets the correct number of rows, but all the cells say "#DELETED"...the data is still there, but Access apparently doesn't know what to do with it.

I don't use Access when I write to the database...I use MySQL Front for writing and administering, and I am unfamiliar with Access. The only reason we are employing it with some of the users is their familiarity with Access, and MS Office.

I am using the most recent MyODBC driver MySQL has on their site. Any suggestions? A setting? What is tripping Access up?

Thanks in advance for the help

[cdthomas9]

Access wants a 'timestamp' filed within your database. just add this field into your table, you dont even need to include it in any forms or reports, access just needs to see times on fileds for some reason.

[tisource]

It's Microsoft Jet Engine drivers....XP needs Jet 4.0 SP6 and then it is supposed to work perfectly. Microsoft's support site describes the exact problem I have, so I expect everything to work perfectly, but I haven't tried the fix quite yet.

If it fails I'll post a note....