persistence for to me... CFC is a matter of preference.
> this sounds like a good excuse to build a persistant cfc
> component.
> ---------- Original Message
> ----------------------------------
> From: Arden Weiss <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> Date: Sat, 07 Aug 2004 22:43:43 -0400
>>In many cases I have a master form/page with a dozen or so
>>fields.
>>
>>On the master form/page I also have one or more buttons
>>that call sub-forms/pages for purposes of maintaining
>>multiple records associated with the master form/record
>>(in a one to many relationship).
>>
>>The question I have is "What is the best practice to use
>>to maintain state in the master form/page while working
>>with the sub-form/pages -- so any changes that have been
>>made in the fields on the master form/page re-appear when
>>the master form/page reloads?
>>
>>Right now I am using client scoped variables to do the
>>trick to avoid using cflock with session scoped variables.
>>
>>Is this the best practice or is another approach
>>mo-betta???
>>
s. isaac dealey 954.927.5117
new epoch : isn't it time for a change?
add features without fixtures with
the onTap open source framework
http://www.sys-con.com/story/?storyid=44477&DE=1
http://www.sys-con.com/story/?storyid=45569&DE=1
http://www.fusiontap.com
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
