From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | "Christopher R(dot) Jones" <cj(at)interlog(dot)com> |
Cc: | pgsql-interfaces(at)postgreSQL(dot)org |
Subject: | Re: [INTERFACES] Access 2000 and ODBC |
Date: | 2000-02-03 16:47:45 |
Message-ID: | 3899B131.1C162DE2@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
> 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(at)alumni(dot)caltech(dot)edu
South Pasadena, California
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Mount | 2000-02-03 16:59:04 | RE: [INTERFACES] Access 2000 and ODBC |
Previous Message | Christopher R. Jones | 2000-02-03 16:16:56 | RE: [INTERFACES] Access 2000 and ODBC |