I agree. I run both, but for export of tables, I have a separate machine set
up to do that.
-----Original Message-----
From: John Calder [mailto:john@stripped]
Sent: Thursday, March 23, 2000 2:24 PM
To: myodbc@stripped
Subject: RE: Converting Access tables to MySQL data on Unix
At 09:41 23/03/00 -0000, you wrote:
>Does MyODBC work with Access 2000? I've installed it but am having trouble
>getting it to work.
>
Read the list archive for recent threads on this topic.
My own experience is that it works "read-only" and refuses to write.
Other writers on the list report it is OK but only if you
add Timestamp fields to every MySQL table.
Access 2000 is getting a lot of criticism in wider discussion
areas for its lack of flexibility. Check out
"Visual Basic Programmers Journal" at www.devx.com
for some criticism of its refusal to work with the
Data Access classes that Microsoft has introduced in VB6.
It is not only the MySQL community that is having trouble!
I'm staying with Access 97 in the meantime, but I am going
to be forced to tackle this problem soon. I hope I will be
able to switch Access 2000 to the older DAO data access system
which is well proven with MySQL.
If I add timestamp fields to all my MySQL tables, will I break
all my existing code which uses "REPLACE INTO tablename VALUES(..."
because my VALUES list will then be one item too short ?!
Regards, John
---------------------------------------------------------------------
Please check "http://www.mysql.com/Manual_chapter/manual_toc.html" before
posting. To request this thread, e-mail myodbc-thread1394@stripped
To unsubscribe, send a message to the address shown in the
List-Unsubscribe header of this message. If you cannot see it,
e-mail myodbc-unsubscribe@stripped instead.
