pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedRe: Insight ODBC driver
4+ messages / 4 participants
[nested] [flat]
* Re: Insight ODBC driver
@ 1998-04-16 16:53 The Hermit Hacker <scrappy@hub.org>
0 siblings, 2 replies; 4+ messages in thread
From: The Hermit Hacker @ 1998-04-16 16:53 UTC (permalink / raw)
To: postodbc-users@listserv.direct.net; +Cc: pgsql-interfaces; mittelstaedt@fh-ulm.de
Please note that postodbc-users@listserv.direct.net is no longer
considered the *official* support channel for the ODBC driver...
Reposting to pgsql-interfaces@postgresql.org
On Thu, 16 Apr 1998, Olaf Mittelstaedt wrote:
> Hello all,
>
> after installation of PostgreSQL 6.3.1 and the newest Insight ODBC
> driver there's only one problem left: when using Access 2.0 (or MS
> Query 1.0) on a Windows NT 4.0 system all tables are read only, even
> if a unique index is present.
>
> Any hints appreciated.
>
> 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.
>
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: [INTERFACES] Re: Insight ODBC driver
@ 1998-04-16 18:36 Byron Nikolaidis <byronn@insightdist.com>
parent: The Hermit Hacker <scrappy@hub.org>
1 sibling, 0 replies; 4+ messages in thread
From: Byron Nikolaidis @ 1998-04-16 18:36 UTC (permalink / raw)
To: pgsql-interfaces@hub.org; mittelstaedt@fh-ulm.de
Olaf,
Did you check to see if the 'ReadOnly' checkbox was selected in the data
source configuration. This is a new feature of the driver and it does
default
to readonly. This is available on the Data Source configuration dialog
box
and the File DSN configuration box. I'm not sure which one you are using.
Byron
The Hermit Hacker wrote:
> Please note that postodbc-users@listserv.direct.net is no longer
> considered the *official* support channel for the ODBC driver...
>
> Reposting to pgsql-interfaces@postgresql.org
>
> On Thu, 16 Apr 1998, Olaf Mittelstaedt wrote:
>
> > Hello all,
> >
> > after installation of PostgreSQL 6.3.1 and the newest Insight ODBC
> > driver there's only one problem left: when using Access 2.0 (or MS
> > Query 1.0) on a Windows NT 4.0 system all tables are read only, even
> > if a unique index is present.
> >
> > Any hints appreciated.
> >
> > 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.
> >
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: [INTERFACES] Re: Insight ODBC driver
@ 1998-04-16 18:49 David Hartwig <daveh@insightdist.com>
parent: The Hermit Hacker <scrappy@hub.org>
1 sibling, 1 reply; 4+ messages in thread
From: David Hartwig @ 1998-04-16 18:49 UTC (permalink / raw)
To: pgsql-interfaces@hub.org; mittelstaedt@fh-ulm.de; +Cc: postodbc-users@listserv.direct.net; pgsql-interfaces
The Hermit Hacker wrote:
> Please note that postodbc-users@listserv.direct.net is no longer
> considered the *official* support channel for the ODBC driver...
>
> Reposting to pgsql-interfaces@postgresql.org
>
> On Thu, 16 Apr 1998, Olaf Mittelstaedt wrote:
>
> > Hello all,
> >
> > after installation of PostgreSQL 6.3.1 and the newest Insight ODBC
> > driver there's only one problem left: when using Access 2.0 (or MS
> > Query 1.0) on a Windows NT 4.0 system all tables are read only, even
> > if a unique index is present.
> >
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.
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.
Attachments:
vcard.vcf (text/x-vcard, 202B) download
begin: vcard
fn: David Hartwig
n: Hartwig;David
email;internet: daveh@insightdist.com
x-mozilla-cpt: ;0
x-mozilla-html: FALSE
version: 2.1
end: vcard
* Re: [INTERFACES] Re: Insight ODBC driver
@ 1998-04-17 07:14 Olaf Mittelstaedt <mstaedt@va-sigi.va.fh-ulm.de>
parent: David Hartwig <daveh@insightdist.com>
0 siblings, 0 replies; 4+ messages in thread
From: Olaf Mittelstaedt @ 1998-04-17 07:14 UTC (permalink / raw)
To: pgsql-interfaces
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.
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~1998-04-17 07:14 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1998-04-16 16:53 Re: Insight ODBC driver The Hermit Hacker <scrappy@hub.org>
1998-04-16 18:36 ` Byron Nikolaidis <byronn@insightdist.com>
1998-04-16 18:49 ` David Hartwig <daveh@insightdist.com>
1998-04-17 07:14 ` Olaf Mittelstaedt <mstaedt@va-sigi.va.fh-ulm.de>
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