Received: from bologna.nettuno.it (bologna.nettuno.it [193.43.2.1])
	by hub.org (8.9.3/8.9.3) with ESMTP id JAA69561
	for <pgsql-interfaces@hub.org>; Wed, 5 May 1999 09:45:19 -0400 (EDT)
	(envelope-from jose@sferacarta.com)
Received: from proxy.sferacarta.com (mail@sfcabop1.nettuno.it
 [193.207.10.213])
	by bologna.nettuno.it (8.8.6/8.8.6/NETTuno 3.1) with ESMTP id PAA04179;
	Wed, 5 May 1999 15:44:53 +0200 (MDT)
Received: from rosso.sferacarta.com (sferacarta.com) [10.20.30.5]
	by proxy.sferacarta.com with esmtp (Exim 2.05 #1 (Debian))
	id 10f3f7-0006ox-00; Wed, 5 May 1999 15:32:41 +0000
Message-ID: <3730486D.222A984E@sferacarta.com>
Date: Wed, 05 May 1999 15:32:29 +0200
From: =?iso-8859-1?Q?Jos=E9?= Soares <jose@sferacarta.com>
X-Mailer: Mozilla 4.5 [it] (Win95; I)
X-Accept-Language: it
MIME-Version: 1.0
To: JT Kirkpatrick <jt-kirkpatrick@mpsllc.com>
CC: "psql-interfaces@hub.org'\" \"" <pgsql-interfaces@hub.org>
Subject: Re: [HACKERS] RE: [INTERFACES] error message
References: <01BE9622.7BAAD400.jt-kirkpatrick@mpsllc.com>
Content-Type: multipart/alternative;
	boundary="------------A0CFB5C9000EBF03A47C925F"


--------------A0CFB5C9000EBF03A47C925F
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit



JT Kirkpatrick ha scritto:

> i do have a few fields (combo boxes based on a query) that sorted on a
> calculated field -- but they seem to work fine in other forms.  --don't
> think that was it.  but, based on your postulations i re-did a few of the
> queries to NOT sort on the calculated fields.  still bombed though. . .
>  so, i deleted the link to the particular table, and then re-linked to it,
> and to my surprise, i can now pull up the form without it bombing.  i can
> even zip through all the records (36k of them) if i wish.  but now it still
> has a problem -- the recordset is not updateable.  if i open the table
> directly (not through any query, and again, from within access97, pgsql
> 6.4.2), the table itself is not updateable.  the table DOES have a primary
> key -- a DUAL FIELD primary key.  I found over the last few weeks that
> Access97 will treat any ODBC table without a primary key defined as not
> updateable, but will it also do the same for DUAL FIELD primary key ODBC
> tables??  it appears so, but can anyone confirm it??

I'm using also access97 with postodbc 6.40.0005 and PostgreSQL v6.5beta1 and it
works fine and I have primary
keys like:

Table    = figure_pkey
+----------------------------------+----------------------------------+-------+

|              Field               |              Type                | Length|

+----------------------------------+----------------------------------+-------+

| azienda                          | char()                           |    16 |

| tipo                             | char()                           |     2 |

| gruppo                           | int4                             |     4 |

| inizio_attivita                  | date                             |     4 |

+----------------------------------+----------------------------------+-------+

Which version of psqlodbc are you using?
I know that Access uses dynaset or snapshots to connect to database.
- If you attach a table without define a primary key Access connects to the
table as snapshot and you can't write table.
- If you define a primary key then Access connects to the table as dynaset and
you are able to write table.
- You must define primary key during table linkage time.
- If you have the ODBC manager option RECOGNIZE UNIQUE INDEXES checked then you
don't need define it
  because Access recognize the primary key automatically.
- If you have the ODBC manager option READ ONLY checked then all linked tables
are read only.
--
______________________________________________________________
PostgreSQL 6.5.0 on i586-pc-linux-gnu, compiled by gcc 2.7.2.3
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Jose'


--------------A0CFB5C9000EBF03A47C925F
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
&nbsp;
<p>JT Kirkpatrick ha scritto:
<blockquote TYPE=CITE>i do have a few fields (combo boxes based on a query)
that sorted on a
<br>calculated field -- but they seem to work fine in other forms.&nbsp;
--don't
<br>think that was it.&nbsp; but, based on your postulations i re-did a
few of the
<br>queries to NOT sort on the calculated fields.&nbsp; still bombed though.
. .
<br>&nbsp;so, i deleted the link to the particular table, and then re-linked
to it,
<br>and to my surprise, i can now pull up the form without it bombing.&nbsp;
i can
<br>even zip through all the records (36k of them) if i wish.&nbsp; but
now it still
<br>has a problem -- the recordset is not updateable.&nbsp; if i open the
table
<br>directly (not through any query, and again, from within access97, pgsql
<br>6.4.2), the table itself is not updateable.&nbsp; the table DOES have
a primary
<br>key -- a DUAL FIELD primary key.&nbsp; I found over the last few weeks
that
<br>Access97 will treat any ODBC table without a primary key defined as
not
<br>updateable, but will it also do the same for DUAL FIELD primary key
ODBC
<br>tables??&nbsp; it appears so, but can anyone confirm it??</blockquote>
I'm using also access97 with postodbc 6.40.0005 and PostgreSQL v6.5beta1
and it works fine and I have primary
<br>keys like:<tt></tt>
<p><tt>Table&nbsp;&nbsp;&nbsp; = figure_pkey</tt>
<br><tt>+----------------------------------+----------------------------------+-------+</tt>
<br><tt>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Field&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
| Length|</tt>
<br><tt>+----------------------------------+----------------------------------+-------+</tt>
<br><tt>| azienda&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
| char()&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp; 16 |</tt>
<br><tt>| tipo&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
| char()&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp; 2 |</tt>
<br><tt>| gruppo&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
| int4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp; 4 |</tt>
<br><tt>| inizio_attivita&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
| date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp; 4 |</tt>
<br><tt>+----------------------------------+----------------------------------+-------+</tt>
<p>Which version of psqlodbc are you using?
<br>I know that Access uses dynaset or snapshots to connect to database.
<br>- If you attach a table without define a primary key Access connects
to the table as snapshot and you can't write table.
<br>- If you define a primary key then Access connects to the table as
dynaset and you are able to write table.
<br>- You must define primary key during table linkage time.
<br>- If you have the ODBC manager option RECOGNIZE UNIQUE INDEXES checked
then you don't need define it
<br>&nbsp; because Access recognize the primary key automatically.
<br>- If you have the ODBC manager option READ ONLY checked then all linked
tables are read only.
<br>--
<br>______________________________________________________________
<br>PostgreSQL 6.5.0 on i586-pc-linux-gnu, compiled by gcc 2.7.2.3
<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
<br>Jose'
<br>&nbsp;</html>

--------------A0CFB5C9000EBF03A47C925F--