From: Keith Worthington <KeithW@NarrowPathInc.com>
To: Zlatko Matic <zlatko.matic1@sb.t-com.hr>
Cc: pgsql-general@postgresql.org
Cc: pgsql-interfaces@postgresql.org
Subject: Re: [INTERFACES] calculated identity field in views, again...
Date: Wed, 04 May 2005 06:57:16 -0400
Message-ID: <4278AA8C.6050502@NarrowPathInc.com> (raw)
In-Reply-To: <002e01c55087$74e44090$c5861dc3@zlatkovyfkpgz6>
References: <20050503151626.37630.qmail@web52405.mail.yahoo.com>
<4277EAEF.5030707@mailblocks.com>
<001201c5502c$1c030430$2d8b1dc3@zlatkovyfkpgz6>
<42784864.4060408@NarrowPathInc.com>
<002e01c55087$74e44090$c5861dc3@zlatkovyfkpgz6>
>> 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
>>
> Zlatko Matic wrote:
> You mean VB.NET ?
Actually we wrote our interface using VB6.
--
Kind Regards,
Keith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: KeithW@NarrowPathInc.com, zlatko.matic1@sb.t-com.hr, pgsql-general@postgresql.org
Subject: Re: [INTERFACES] calculated identity field in views, again...
In-Reply-To: <4278AA8C.6050502@NarrowPathInc.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox