MyODBC and Access: empty table works, filled shows errors
am 17.12.2007 21:12:53 von Mark JansenHi all,
Ive done quite some things with MyODBC, but I really dont know what to
do with this case. Hopefully you can help.
I've made a database in Access to manage all the administration for our
orchestra. For the latest version I programmed a download/upload macro,
in order to send or retrieve the data from our website (but all the data
were stored locally).
Since all of the board members nowadays have a high speed broadband
connection, I want to switch to an all-online version of this database
(so no more manual uploading).
So I created all the tables online and inserted all the data using
PhpMyAdmin and linked these tables to an Access database.
All seems to go fine, but I have this problem with just one table. I can
most easily describe its structure with the CREATE query (thank to
phpMyAdmin)
CREATE TABLE `Functie-aan-lid` (
`ID` int(11) NOT NULL auto_increment,
`LidID` int(11) default NULL,
`FunctieID` int(11) default NULL,
`Gewijzigd` timestamp NULL default CURRENT_TIMESTAMP,
PRIMARY KEY (`ID`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1 CHECKSUM=1 AUTO_INCREMENT=263 ;
This is a n-to-n table, so multiple flexible relations. Lid is the Dutch
word for member, so LidID is the MemberID (data of members stored in
another table). FunctieID refer to the sections of the club the
members belong to (ranging from just 1 to many more).
The problem is: when this table is empty, Access shows it perfectly to
me. I can also easily add data, no problem at all. I just tried to enter
three rows to test this.
However, once I paste the current n-to-n relationship data into this
table (n=260) and reopen the table, Access comes with an ODBC error and
stops. All the columns show #NAME (actually #NAAM in Dutch). The odd
thing is: Access shows the data perfectly right after pasting, but once
I reopen the table, the trouble is back again.
It doesnt make any difference whether I paste the data using Acccess or
using phpMyAdmin. I tried all sorts of MyODBC connection parameters, but
none seem to have any effect.
Does anyone have a clue?? Thanks!
--
Met vriendelijke groet,
Mark Jansen
E. info@markjansen.nl
M. (+31) (0)6 48 35 10 42
W. http://www.markjansen.nl
F. (+31) (0) 87 78 441 26
--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc@m.gmane.org