Re: Forms5/6i: any benefits using NAME_IN instead of bind variable ?
From: Frank van Bortel <fvanbortel_at_netscape.net>
Date: Wed, 14 Apr 2004 21:51:53 +0200
Message-ID: <c5k4jc$qqf$1_at_news5.tilbu1.nb.home.nl>
Date: Wed, 14 Apr 2004 21:51:53 +0200
Message-ID: <c5k4jc$qqf$1_at_news5.tilbu1.nb.home.nl>
Jan Gelbrich wrote:
> OK, thatīs an argument.
> But for a "normal" tiny PU or a Forms Trigger containing 20 lines ?
>
> "Fred van Nimwegen" <fred.vannimwegen_at_wanadoo.nl> schrieb im Newsbeitrag
> news:407c41ae$0$64611$4a441750_at_news.wanadoo.nl...
>
>>In librarys Name_in and Copy are the only options.
>>
No.
But as soon as you want something done dymanically
(e.g. traverse a block, and find out what fields
need what attribute(s) set), name_in is a powerful
option.
If you ever get the opportunity to check out the
code of Headstart 3.4, you'll see what I mean.
(for those wondering: Headstart were the templates for Designer/2000, back when it was called Des/2000)
-- Regards, Frank van BortelReceived on Wed Apr 14 2004 - 21:51:53 CEST