From: Thomas Lockhart <lockhart@alumni.caltech.edu>
To: Christopher R. Jones <cj@interlog.com>
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Access 2000 and ODBC
Date: Thu, 03 Feb 2000 16:47:45 +0000
Message-ID: <3899B131.1C162DE2@alumni.caltech.edu> (raw)
References: <3.0.32.20000203111652.00a16290@mail.interlog.com>
> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: lockhart@alumni.caltech.edu, cj@interlog.com
Subject: Re: [INTERFACES] Access 2000 and ODBC
In-Reply-To: <3899B131.1C162DE2@alumni.caltech.edu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox