Forms 4.5 - Removing/hiding records in Post-query ??

[Henrik Krievs]

Hi' NG !

Based on a calculated field (calculated in post-query) - I'd like to
supress/hide/not show - some off the records in the selected set. How is
that done ?

I've tried at raise form_trigger_failure in post_query, but it on stops the
calculation - not the showing of the record.

Any ideas ??

BR, Henrik

[Alex Filonov]

Here is one, clumsy though:

use mirrored blocks. One block is a database block, hidden (not
visible). Another block is visible, non-database. You'll have to
manually define all operations in this form. For example, you'll have
to have pre-query on non-database block to define query in database
block. Then in post-query you copy rows from database block to non-
database one based on any condition you want. Sound pretty complex and
ugly? Then another solution:

TRY TO SET A RIGHT QUERY CONDITION IN PRE-QUERY. I don't think it's too
hard to do.

In article <qaKW5.73$8T....@news.get2net.dk>,

Sent via Deja.com http://www.deja.com/
Before you buy.

[Matt B.]

"Henrik Krievs" <wm...@dffe.dk> wrote in message
news:qaKW5.73$8T....@news.get2net.dk...

> Hi' NG !
>
> Based on a calculated field (calculated in post-query) - I'd like to
> supress/hide/not show - some off the records in the selected set. How is
> that done ?
>
> I've tried at raise form_trigger_failure in post_query, but it on stops the
> calculation - not the showing of the record.
>
> Any ideas ??
>
> BR, Henrik

Just a guess, and this might fire too often and in cases where you don't want
it to, but try it anyway.

On WHEN-NEW-RECORD-INSTANCE, try this:

IF :SYSTEM.LAST_RECORD = 'TRUE' AND
:SYSTEM.RECORD_STATUS = 'QUERY' AND
<TRUE boolean condition for your calculation> THEN
clear_record;
END IF;

-Matt

[Luc Bosman]

On Mon, 4 Dec 2000 11:19:06 +0100, "Henrik Krievs"
<wm...@dffe.dk> wrote:

>Hi' NG !
>
>Based on a calculated field (calculated in post-query) - I'd like to
>supress/hide/not show - some off the records in the selected set. How is
>that done ?
>
>I've tried at raise form_trigger_failure in post_query, but it on stops the
>calculation - not the showing of the record.

Easy, in the post query trigger do something like

result := your compute;
if result < 100 then
raise form_trigger_failure;
end if;

I use this method when the where clause become too heavy to
maintain or too much costing for the database (like some 'exists'
in various tables test).
Are you sure of your coding?

--
Luc Bosman
DEV/2000 Software Engineer
Database & Network Administrator
l.bo...@wanadoo.be ICQ 37011625
http://users.skynet.be/kobukai/
----------------------------------------------------
| -°) (°- |
| /\\ Linux the choice of the GNU generation //\ |
| _\_v v_/_ |
----------------------------------------------------

[Henrik Krievs]

Tried that one, It doesn't seem to work. We use Headstart, so all the code
is placed in lib's.

Br, Henrik

Luc Bosman skrev i meddelelsen
<8v8p2tgj07u2fis5e...@4ax.com>...