Re: forms 4.5; visual attribute

USE DISPLAY_ITEM builtin

In <322B110E.F17_at_ix.netcom.com> Loyal Barber <lbarber_at_ix.netcom.com> writes:
>
>Grant Donohoe wrote:
>>
>> Loyal Barber wrote:
>> >
>> > Franco Rizzo wrote:
>> > >
>> > > How can I to modify the visual attribute of a record in a
 multi-line block
>> > > (not the current record),
>> > > like report 2.5 ?
>> > >
>> > > thank you.
>> > Attributes are only available at three levels:
>> > item (column)
>> > current record
>> > in short, you can't
>>
>> Hi,
>>
>> If you have a way of identifying or storing which record you wanted
 to
>> change couldn't you navigate to the appropriate record, set the
>> attributes of what would then be the current record then go back
 where
>> you have just come from. There are restrictions on which events can
>> trigger navigation (look up restricted packaged procedures,
 go_record is
>> one though) but I'm sure you could work round any difficulties, even
 if
>> it was a little clumsy.
>>
>> So for example if you wanted to set the first record in the block to
 red
>> whenever another record had a value over $50 entered in a certain
 field.
>>
>> Thus without regard to syntax..
>>
>> if :go_field > 50 then...
>>
>> :control_block.rec_number := :system.cursor_record;
 (or)
>> :control_block.rec_number := :system.trigger_record;
>>
>> FIRST_RECORD;
>> (or)
>> GO_RECORD(:control_block.rec_number + 4)
>> If you wanted to move about by a certain amount
>> (or)
>> FIRST_RECORD
>> check for a particular attribute, flag or value
>> NEXT_RECORD
>> check again
>> NEXT_RECORD
>> until you find the record you want.
>>
>> SET_ATTRIBUTE......etc'
>> go_record(:CONTROL_BLOCK.REC_NUMBER);
>> :control_block.rec_number := NULL;
>>
>> Problem is triggering this as I don't think you can do it from say a
>> WHEN-VALIDATE-ITEM,but there are tricks to get round this e.g firing
 it
>> from an on-new-item-instance trigger on the next navigable field
 (and
>> maybe setting autoskip on in the $50 field to avoid mouse navig)
 Also you
>> have to be careful the navigation doesnt fail due to triggers on the
>> record you are moving away from. Also I think when you set an
 attribute
>> in your target record that record may be re-validated (not sure on
 that
>> though)
>>
>> GOOD LUCK, THESE PROBLEMS ARE WHAT MAKES FORMS SUCH FUN :-)
>>
>> Grant Donohoe.
>Problem is, this solution won't work. As soon as you navigate to
>another record, the record where you changed the current record
>attribute
>is no longer the current record. therefore the attribute will
>change back to the default.
Received on Tue Sep 03 1996 - 00:00:00 CEST