Skip site navigation (1) Skip section navigation (2)

RE: [INTERFACES] MSAccess and primary keys

From: Michael J Davis <michael(dot)j(dot)davis(at)tvguide(dot)com>
To: "'leif(at)danmos(dot)dk'" <leif(at)danmos(dot)dk>, pgsql-interfaces(at)postgreSQL(dot)org
Subject: RE: [INTERFACES] MSAccess and primary keys
Date: 1999-05-15 16:23:58
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
Make sure the "Recognize Unique Indexes" flag is turned on in the PostgreSQL
ODBC driver.

	-----Original Message-----
	From:	leif(at)danmos(dot)dk [SMTP:leif(at)danmos(dot)dk]
	Sent:	Saturday, May 15, 1999 2:35 AM
	To:	pgsql-interfaces(at)postgreSQL(dot)org
	Subject:	[INTERFACES] MSAccess and primary keys

	 [Sorry for reposting this, the subject got garbled.]


	  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) 



pgsql-interfaces by date

Next:From: Keith/Suzanne BarronDate: 1999-05-15 16:24:56
Subject: Problem loading jdbc driver in servlet, but not in program
Previous:From: Geoffrey C. SpeicherDate: 1999-05-15 13:19:03
Subject: Re: [INTERFACES] MSAccess and primary keys

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group