Message-ID: <42784864.4060408@NarrowPathInc.com>
Date: Tue, 03 May 2005 23:58:28 -0400
From: Keith Worthington <KeithW@NarrowPathInc.com>
Reply-To: KeithW@NarrowPathInc.com
Organization: Narrow Path, Inc.
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: Zlatko Matic <zlatko.matic1@sb.t-com.hr>
Cc: pgsql-general@postgresql.org, pgsql-interfaces@postgresql.org
Subject: Re: [INTERFACES] calculated identity field in views, again...
References: <20050503151626.37630.qmail@web52405.mail.yahoo.com>
	<4277EAEF.5030707@mailblocks.com>
	<001201c5502c$1c030430$2d8b1dc3@zlatkovyfkpgz6>
In-Reply-To: <001201c5502c$1c030430$2d8b1dc3@zlatkovyfkpgz6>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Zlatko Matic wrote:
> 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.
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
>      joining column's datatypes do not match
> 
> 

Another option is to toss the MS Access altogether and program the front 
end entirely in VB.  That is what we did.

-- 
Kind Regards,
Keith