Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250])
	by hub.org (8.10.1/8.10.1) with ESMTP id e7J0q2m48002
	for <pgsql-interfaces@postgresql.org>;
	Fri, 18 Aug 2000 20:52:02 -0400 (EDT)
Received: from [209.10.40.250] (account <josh@agliodbs.com>)
	by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.3)
	with HTTP id 1081100 for <pgsql-interfaces@postgresql.org>;
	Fri, 18 Aug 2000 17:52:01 -0700
From: "Josh Berkus" <josh@agliodbs.com>
Subject: Re: MS Access problems
To: pgsql-interfaces@postgresql.org
X-Mailer: CommuniGate Pro Web Mailer v.3.3
Date: Fri, 18 Aug 2000 17:52:01 -0700
Message-ID: <web-1081100@davinci.ethosmedia.com>
In-Reply-To: <399DAA34.A4870D95@albourne.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Archive-Number: 200008/111

Mr. Nanni,

> The problems are:
>   1. when linking a table, Access is unable to find
> automatically the
>      primary key and raises a dialog asking me to specify
> it.

This is an MS Access problem.  Access is rarely able to
automatically discern primary or foriegn keys in ODBC
databases.  I have the same problem with attaching MS SQL
Server tables, which are supposedly 100% compatible.

>   2. Access is unable to discover automatically
>      relations and foreign keys in the database.

See Above.

You're going to have to settle for specifying the primary
key on creation of the linked table, and re-creating the
foriegn keys on the client side, or simply coding in the
referential integrity.

-Josh Berkus