Received: from localhost (IDENT:root@hectic-2.jpl.nasa.gov [128.149.68.204]) by hub.org (8.9.3/8.9.3) with ESMTP id LAA94016 for ; Thu, 3 Feb 2000 11:40:08 -0500 (EST) (envelope-from lockhart@alumni.caltech.edu) Received: from alumni.caltech.edu (lockhart@localhost [127.0.0.1]) by localhost (8.8.7/8.8.7) with ESMTP id QAA08674; Thu, 3 Feb 2000 16:47:45 GMT Sender: lockhart@hub.org Message-ID: <3899B131.1C162DE2@alumni.caltech.edu> Date: Thu, 03 Feb 2000 16:47:45 +0000 From: Thomas Lockhart X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i686) X-Accept-Language: en MIME-Version: 1.0 To: "Christopher R. Jones" CC: pgsql-interfaces@postgreSQL.org Subject: Re: [INTERFACES] Access 2000 and ODBC References: <3.0.32.20000203111652.00a16290@mail.interlog.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > Interestingly enough, this thread is also very active on the MySQL mailing > list. It seems that ACCESS 2000 has a bug that makes many ODBC datasources > read only. Some MySQL tables linked to Access 2000 via ODBC are read/write > and some are not. Note that if the tables are converted to Foxpro tables > (use same column types) then Access has no problem. Hopefully Microsoft > will pay attention. I've worked just a bit with ODBC, but not with any of the front end tools you are discussing. But I vaguely recall some discussion on the list that some tool (Access?) required that there be a primary key defined to allow a table to be considered writable. Does this ring a bell with anyone? If not, sorry for the misdirection... - Thomas -- Thomas Lockhart lockhart@alumni.caltech.edu South Pasadena, California