X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 1A51A534BF; Tue, 3 May 2005 19:04:47 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 08554-01; Tue, 3 May 2005 22:04:44 +0000 (GMT) Received: from ls405.htnet.hr (ls405.htnet.hr [195.29.150.97]) by svr1.postgresql.org (Postfix) with ESMTP id A7FA152A82; Tue, 3 May 2005 19:04:41 -0300 (ADT) Received: from ls413.htnet.hr (ls413.htnet.hr [195.29.150.117]) by ls405.htnet.hr (0.0.0/8.12.10) with ESMTP id j43M4gwV023146; Wed, 4 May 2005 00:04:42 +0200 Received: from ls413.htnet.hr (localhost.localdomain [127.0.0.1]) by ls413.htnet.hr (Qmali) with ESMTP id 6F5D6AC004; Wed, 4 May 2005 00:04:42 +0200 (CEST) Received: from zlatkovyfkpgz6 (ad11-m45.net.t-com.hr [195.29.139.45]) by ls413.htnet.hr (Qmali) with SMTP id 4890DEC006; Wed, 4 May 2005 00:04:41 +0200 (CEST) Message-ID: <001201c5502c$1c030430$2d8b1dc3@zlatkovyfkpgz6> From: "Zlatko Matic" To: , References: <20050503151626.37630.qmail@web52405.mail.yahoo.com> <4277EAEF.5030707@mailblocks.com> Subject: calculated identity field in views, again... Date: Wed, 4 May 2005 00:04:41 +0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="ISO-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 1 X-MSMail-Priority: High X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.106 tagged_above=0 required=5 tests=AWL, X_MSMAIL_PRIORITY_HIGH, X_PRIORITY_HIGH X-Spam-Level: X-Archive-Number: 200505/149 X-Sequence-Number: 77497 I asked this question several weeks ago, but nobody proposed a solution, so I am repeating the same question again... I have an MS Access front-end for a database on PostgreSQL. I could use pass-through queries as record sources for reports and it works fine... Unfortunately, MS Access doesn't allow pass-through queries to be records sources for subforms. Therefore I tried to base subforms on regular JET queries on linked tables. It was too slow... Then I tried to base subforms on DAO recordset code generated from pass-through QueryDef objects. Although it worked, it was very unstable... Now it seems to me that POstgreSQL views are the best solution, but Access considers views as tables (!) and needs column with unique values. All those views are complicated queries on several tables, so I can't use any table's column as primary key. I need a calculated column in the view that Access will consider as primary key column. In regular tables, I use bigserial field, but how can I create calculated bigserial column in a view ? Thanks.