Re: Skipping fields in SQL*Forms V3

From: <ballpe_at_cnb07v.hhcs.gov.au>
Date: 24 Sep 93 08:30:07 +1000
Message-ID: <1993Sep24.083007.1_at_cnb07v.hhcs.gov.au>


In article <rchanceCDrLEt.CAJ_at_netcom.com>, rchance_at_netcom.com (Ray Chance) writes: <Stuff Deleted>
>
> I'd use a pre-field trigger on the field in question, and then in the
> trigger set the attribute of the field based on your record criteria.
> ex: if (:system.record_status in ('NEW','INSERT')) then
> set_field(:<field_in_question>,enterable,attr_off);
> end if;
> I'm not 100% certain of my syntax, but you get the idea. Pre-field will
> fire no matter which direction you approach the field (previous or next),
> and setting the attribute will have forms skip over it appropriately.
> RC

Ray,

I think PRE-FIELD will not work to do this. The field context is already set by the time this trigger fires and Forms won't let you set the attribute of the current field.

It is a while since I did this sort of stuff, but I wouldn't try setting the attributes of a field with a trigger for that field. I reckon it should be set before any navigation to the field.

-- 

    /\       Peter Ball                 (ballpe_at_hhcs.gov.au)
   /  \      Systems Development Officer
  /    \     Dept Health, Housing, Local Govt and Community Services
 /      \    Brisbane, Queensland, Australia
/   /    \   "The views expressed above are mine and mine alone"
\  / /   /
 \/ / / /    Telephone : (07) 360 2637
  \/ / /     Postal    : Information Services Section
   \/ /                  GPO Box 9848
    \/                   Brisbane QLD 4001
                         Australia
Received on Fri Sep 24 1993 - 00:30:07 CEST

Original text of this message