Received: from mail.crysberg.dk (root@square.crysberg.dk [194.192.196.2]) by hub.org (8.9.3/8.9.3) with ESMTP id EAA26098 for ; Sat, 15 May 1999 04:34:47 -0400 (EDT) (envelope-from leif@danmos.dk) From: leif@danmos.dk Received: from crysberg.dk (root@samba.crysberg.dk [194.192.196.12]) by mail.crysberg.dk (8.8.5/8.8.5) with ESMTP id KAA22942 for ; Sat, 15 May 1999 10:40:12 +0200 Received: from danmos.dk (cdslj.crysberg.dk [194.192.196.20]) by crysberg.dk (8.8.7/8.8.7) with SMTP id KAA28939 for ; Sat, 15 May 1999 10:34:45 +0200 Date: Sat, 15 May 1999 10:34:45 +0200 Message-Id: <199905150834.KAA28939@crysberg.dk> To: pgsql-interfaces@postgreSQL.org Subject: [INTERFACES] MSAccess and primary keys Content-Type: text [Sorry for reposting this, the subject got garbled.] Hello, I have a rather anoying problem. I am linking a quite large M$Access application to a PostgreSQL database with a a lot of relations (primary keys/foreign keys). In all my tables I have created primary keys (to keep M$Access happy ;-). Unfortunately, when I link my application to the database, Access asks me for each and every table (there are more than 80 of them) what I want to use for unique index field. I thought the primary key spec would do just that? All tables are designed like the one below: create table globalafvigelse ( id serial , startdato date, slutdato date, dagskema varchar(50), primary key (globalafvigelse) ); Greetings, Leif (leif@danmos.dk)