From: Olaf Mittelstaedt <mstaedt@va-sigi.va.fh-ulm.de>
To: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Re: Insight ODBC driver
Date: Fri, 17 Apr 1998 08:14:44 +0100
Message-ID: <199804170615.IAA01926@gate.va.fh-ulm.de> (raw)
In-Reply-To: <353652BC.C5474A4D@insightdist.com>
Thank you Byron and David for your answers (and Marc for redirecting
my message to pqsql-interfaces).
Here a few more details on my problem.
> 1. I am not as familiar with Access 2.0. But the 7.0 and 97 versions
> require a unique key to be specified at link time for an update to be
> allowed. I want to be sure that you have done that, and that you not
> referring to the "create unique index" statement which creates the index
> in the database table on the server.
Access 2.0 should automatically use a unique index on the database
server if it's present. Below the statements I've used to create,
populate and test the table.
create table test3(i1 int4,i2 int4, i3 int4);
create unique index i_test3_i1 on test3(i1);
insert into test3 values(1,2,3);
insert into test3 values(2,3,4);
insert into test3 values(3,4,5);
\d
Database = vorwahl
+------------------+----------------------------------+----------+
| Owner | Relation | Type |
+------------------+----------------------------------+----------+
| postgres | i_test3_i1 | index |
| postgres | test3 | table |
+------------------+----------------------------------+----------+
\d i_test3_i1
Table = i_test3_i1
+-----------------+----------------------------------+-------+
| ld | Type | Length|
+-----------------+----------------------------------+-------+
| i1 | int4 | 4 |
+-----------------+----------------------------------+-------+
select * from test3;
i1|i2|i3
--+--+--
1| 2| 3
2| 3| 4
3| 4| 5
(3 rows)
insert into test3 values(3,3,3);
ERROR: Cannot insert a duplicate key into a unique index
After linking the table above to an Access 2.0 database I can see the index,
but Access thinks it's not unique.
> 2. There is a read-only check box on the data source setup dialog. This was
> put in to prevent unintentional key strokes from getting into the database.
> This is remarkably easy to do in MS Access. Just unchecked the box for your
> data source.
The read-only checkbox on the data source dialog is unchecked.
It can't be an authentication problem because if I create a local index
for the linked table I can add/delete rows.
Regards,
Olaf
--
Olaf Mittelstaedt - IuK - mittelstaedt@fh-ulm.de
Fachhochschule Ulm Prittwitzstr. 10 89075 Ulm
Tel.: +49 (0)731-502-8220 Fax: -8270
Tertium non datur.
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: mstaedt@va-sigi.va.fh-ulm.de
Subject: Re: [INTERFACES] Re: Insight ODBC driver
In-Reply-To: <199804170615.IAA01926@gate.va.fh-ulm.de>
* 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