MS Access ODBC sees data but can't display it

[Patrick]

Hi all,

I've installed the latest MDAC and Jet service packs on Windows 2000. On
Linux I've the latest MySQL and MyODBC3.51.

Using the ODBC Administrator I've set up a connection, ran the test and
all appears well. I then link to the MySQL tables from Access and again
all appears well. Until I open the table and see that all data is
marked "#DELETED".

To test, I run a few queries which should bring back one record. They
all work.

So Access sees the data but cannot dispaly it. The table does have a
primary key and timestamp - its SQL follows:

CREATE TABLE `tblContacts` (
`p_ID` bigint(11) NOT NULL auto_increment,
`p_Company` int(11) default '2',
`p_FirstName` varchar(255) default NULL,
`p_LastName` varchar(255) default NULL,
`p_JobTitle` varchar(255) default NULL,
`p_DirectLine` varchar(255) default NULL,
`p_Mobile` varchar(255) default NULL,
`p_HomeNumber` varchar(255) default NULL,
`p_WorkEmail` varchar(255) default NULL,
`p_PrivateEmail ` varchar(255) default NULL,
`p_Notes` varchar(255) default NULL,
`p_CandidateCV` mediumblob NOT NULL,
`p_EHR_CV` mediumblob NOT NULL,
`p_Grouping` enum('None','Ma nager','Develop er','Producer') NOT NULL
default 'Developer',
`p_CoreSkill` enum('None','C+ +','C#') NOT NULL default 'C++',
`c_timestamp` timestamp(14) NOT NULL,
PRIMARY KEY (`p_ID`)
) TYPE=MyISAM AUTO_INCREMENT= 60 ;
Can anyone suggest why Access is not displaying the data correctly?

[Patrick]

Patrick wrote:

Hi all,

CREATE TABLE `tblContacts` (
`p_ID` bigint(11) NOT NULL auto_increment,

Access can't display BIGINT - a simple change to mediumint fixed the
problem.

Thanks to all who gave this some thought.

[Patrick]

Patrick wrote:

Hi all,

CREATE TABLE `tblContacts` (
`p_ID` bigint(11) NOT NULL auto_increment,

Access can't display BIGINT - a simple change to mediumint fixed the
problem.

Thanks to all who gave this some thought.

[Patrick]

Patrick wrote:

Hi all,

CREATE TABLE `tblContacts` (
`p_ID` bigint(11) NOT NULL auto_increment,

Access can't display BIGINT - a simple change to mediumint fixed the
problem.

Thanks to all who gave this some thought.