From: | "Goulet, Dick" <DGoulet(at)vicr(dot)com> |
---|---|
To: | <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: linked tables Access <---> PG 7.4.1 |
Date: | 2004-01-16 15:12:31 |
Message-ID: | 4001DEAF7DF9BD498B58B45051FBEA656D806D@25exch1.vicorpower.vicr.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
Naw, It's just MicroSlop being a stinker.
Dick Goulet
Senior Oracle DBA
Oracle Certified 8i DBA
-----Original Message-----
From: Andreas [mailto:maps(dot)on(at)gmx(dot)net]
Sent: Thursday, January 15, 2004 7:27 PM
To: pgsql-odbc(at)postgresql(dot)org
Subject: [ODBC] linked tables Access <---> PG 7.4.1
Hi,
I fear this might be off-topic but I'm sure I'd be hit, too, if I asked
something concerning the interaction with PostgreSQL on the dark side. ;)
Client: MS-Access 2000
Server: PG 7.4.1
I ODBC-link some tables and all is fine.
Then I manually link a PostgreSQL-view and Access asks which of the
fields will be the primary key of this "table".
Then again, if I link the view with VBA's DAO command
CurrentDB.CreateTableDef( [...] ) no question appears and the view gets
created as a table-object.
If I inspect it's design, there is no field marked as primary key.
Is the PK really obsolete or does it have implications in the
performance of Access or PG ?
Thanks
Andreas
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
From | Date | Subject | |
---|---|---|---|
Next Message | Cristy N. | 2004-01-16 17:31:09 | error 3669 in psql 7.2 |
Previous Message | Jeff Eckermann | 2004-01-16 02:04:19 | Re: linked tables Access <---> PG 7.4.1 |