how do you do it?
looking for a solution, I found this thread just some lines below:
update rules + views + ....
which suggests using ctid, causing problems with views using more than
for views using 2 tables, I found the following partial solution:
1: updatable views need a 'catch all rule'; docs indicate to do
'create or replace rule UpdRuleCatchAll as on update myview do instead
It looks like, this 'nothing' makes access moan about 'no record'.
'do nothing' replaced by:
'do select * from myview where <YourPrimaryKeySpecHere>'
returns 1(!) record. -> no 'record missing' any more.
2: do specific update rules with '...where OLD.YourKey is NULL or
OLD.yourkey <> NEW.yourkey (update or insert the table involved) where
(use exactly the same keys as you will give access as the primary
key(s) when importing the view as a linked table)
didn't try to do insert or delete rules yet; using a form, I just call
a stored procedure on a 'OnClick'-Event that is designed to do what is
needed, and the .Requery of the matching MS-Access-Object.
This works _without_ including ctid in the views definition _and_ it
works with 2 tables involved. (just trying to get the third)
pgsql-odbc by date
|Next:||From: Rodrigo Carvalhaes||Date: 2004-11-07 19:15:08|
|Previous:||From: Lothar Behrens||Date: 2004-11-03 19:41:04|
|Subject: ODBC understanding problem|