Re: Forms4.5: Multi-Record Block
Date: 1998/04/16
Message-ID: <3535C9FF.C20368A2_at_jameswatt.ac.uk>#1/1
Hi.
[Quoted] Since all the items have to be the same, would it not make more sense to store the ship-to field in the master block? However... How about creating a single 'dummy' field in the detail block (ie. NOT a base table item, and 'items displayed' = 1) and use a either a block-level POST-QUERY trigger to populate it with the contents of the real ship-to field, or (easier) set 'mirror item' to point to the real one. Any validation etc. should be also done on the dummy field. Finally, set the 'mirror item' property on the genuine ship-to field (which isn't displayed, BTW) to point to the dummy field.
Jamie Keir
Samatha Reddy wrote:
>
> Hello,
>
> We have a master-detail form, the master block is purchase_orders block and
> multi-record detail block is purchase_order_lines block. This mutli-record
> detail block has ship-to column, we want to enforce single ship-to per each
> purchase order. i.e. all the records in the detail block should have similar
> ship-to. Also user should be allowed to change the ship-to on any record.
> Note: there no ship-to field on the master block.
>
> In this multi-record block, if user changes the ship-to location in any row,
> the form should changed the ship-to location in all remaining records to
> reflect this new value.
>
-- _______________________________________________________________ /###############################################################\ +--------------------+---------------+----------------------------+ | Oracle 7 DBA | Digital Unix | Jamie Keir | | Developer*2000 | Windows NT 4 | jkerr_at_jameswatt.ac.uk | | PL*SQL | AmigaOS 3 | | | Unix Admin | Linux | | | Network Support | ADA | ...now if I could just get | | | C / C++ | them to *pay* me for it... | | Alpha AXP | M68040 Asm | | +--------------------+---------------+----------------------------+Received on Thu Apr 16 1998 - 00:00:00 CEST