Bug #19819 "linking" tables from mysql 4.x from ms-access reveals only #Deleted records
Submitted: 15 May 2006 15:16 Modified: 30 May 2013 7:18
Reporter: Mike Koehler Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / ODBC Severity:S2 (Serious)
Version:3.51 > OS:Microsoft Windows (Win2K)
Assigned to: Miguel Solorzano CPU Architecture:Any

[15 May 2006 15:16] Mike Koehler
Description:
I have been using ms-access as a front-end to several mysql databases and have never had a problem. We recently moved to mysql 4.1 from 3.x and now - while I can still import a table locally into ms access 2000, when I "link" a table inside ms-access, it reveals the data as "#Deleted" in every row and every column.

I have tried using the odbc drivers for 4.1 and 5.x, same problems.

Any info/suggestions would be appreiciated.

Mike

How to repeat:
create new ms-access .mdb
Import/Link tables from odbc source.
select "link"
select "odbc" source
find dsn or user odbc config, select it
Window opens up in ms-access listing off the objects in the mysql database.
select a table.
close window.
open "linked" table.

All values in table just linked appear as "#Deleted"
[15 May 2006 16:41] Miguel Solorzano
Thank you for the bug report. Please read the instructions at:

http://dev.mysql.com/doc/refman/4.1/en/deleted-problem.html

18.1.11.5. When I Insert or Update a Record in Linked Tables, I Get #DELETED#
[15 May 2006 18:29] Mike Koehler
I'm not trying to update or insert at this time, im just doing a select.
I have all the listed switches set on the odbc driver, and it occurs on tables that dont have bigint.
[15 May 2006 18:35] Miguel Solorzano
Thank you for the feedback. Do you have a dummy timestamp column and
a primary key as suggested in the same Manual's section?

#

You should have a timestamp in all tables that you want to be able to update. For maximum portability, don't use a length specification in the column declaration. That is, use TIMESTAMP, not TIMESTAMP(N), N < 14.
#

You should have a primary key in the table. If not, new or updated rows may show up as #DELETED#.
[15 Jun 2006 23:00] Bugs System
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".
[30 May 2013 7:18] Bogdan Degtyariov
I'm closing this bug because I can not continue without feedback from the reporter. If you have new info, please reopen the report.