From: Martin J. Evans
Date: February 3 2006 6:05pm
Subject: RE: #deleted in Access
List-Archive: http://lists.mysql.com/myodbc/10581
Message-Id: <XFMail.20060203180552.martin.evans@easysoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit

I'm not sure about MyODBC but from memory this occurs in Access because it
attempts to retrieve a row with the primary key value (it previously retrieved)
and couldn't find the row (indicating to Access the row has been deleted).

i.e. it does
select primary_key_column from table then retrieves the data with
select a,b,c,d from table where primary_key_column = ?
and fails to retrieve a row.

In actual fact, it tends to retrieve 10 rows at a time with

select a,b,c,d from table where pcc = ? or pcc=? or pcc=? (10 of these).

Not sure if this helps you but it may give you or someone else somewhere to
look.

Martin

On 03-Feb-2006 Rigov wrote:
> 
> 
> I have MySQL 3.21.x and MySQL Connector/ODBC 3.51 and for one of my tables,
> all values show up as #Deleted.  I've followed the directions found under
> Support on mysql.com, but to no avail.  I'm using Access 2003.  
> 
> Here is a definition of the table:
> 
> CREATE TABLE `device_responses` (
>   `id` bigint(20) unsigned NOT NULL auto_increment,
>   `time_tag` bigint(10) unsigned default NULL,
>   `system` enum('D') NOT NULL default 'STE',
>   `device` enum('A', 'B', 'C') NOT NULL default 'HEARTBEAT',
>   `subunit`
> enum('0','1','2','3','4','5','6','7','8','9','10','11','12','13','14','15','16
> ','17','18','19','20','21','22','23') NOT NULL default '0',
>   `sender` enum('0','1','2','3','4','5','6','7','8') default '0',
>   `command` varchar(8) default NULL,
>   `response` varchar(8) default NULL,
>   PRIMARY KEY  (`id`),
>   KEY `(command, response)` (`command`,`response`),
>   KEY `(response, command)` (`response`,`command`),
>   KEY `device` (`device`),
>   KEY `system` (`system`),
>   KEY `sender` (`sender`)
> ) TYPE=InnoDB AUTO_INCREMENT=1 ;
> 
> 
> Other tables have similar properties, and they do not have this problem. 
> This is the only InnoDB table, but even after dropping it, and creating new
> as MyISAM, I had no luck.  Other tables have bigint() and they are okay.
> 
> Any help would be appreciated.
> 
> Thanks
> 
> 
> _______________________________________________
> No banners. No pop-ups. No kidding.
> Make My Way  your home on the Web - http://www.myway.com
> 
> 
> 
> -- 
> MySQL ODBC Mailing List
> For list archives: http://lists.mysql.com/myodbc
> To unsubscribe:   
> http://lists.mysql.com/myodbc?unsub=martin.evans@stripped

--
Martin J. Evans
Easysoft Ltd, UK
http://www.easysoft.com