At the point that you click the link that opens the popup, pass the form fields to the spawned child window. Save the original form data within a hidden form on the popup. When you submit the popup, have the popup form submit back to the originating form. This will allow you to detect for the form scope when rebuilding the page.
A common technique that I use is always for reuseable forms. <cfparam name="form.field" default=""> <input type="text" name="field" value="#form.field#"> What this enables the form to do is be empty on a new form or put in values if a form submission occurs. In essence, you can use the form for both updates and creations. Teddy On 10/13/06, Andrew Peterson <[EMAIL PROTECTED]> wrote: > > Hi Ben. Thanks for your response. One question: > > >What about just signaling the page to SUBMIT rather than REFRESH and set > >some sort of hidden field flag to tell the processing page NOT to > >process the form, but just to let it refresh with the same form data. > >This will allow the form to keep submitting to itself. > > So in this idea does the data need to be stored into some temporary > repository, or is there a way I can tell a browser to refresh itself with > the data in form fields intact? I know that a refresh in Firefox keeps > whatever form data I put in there originally, which is great, but IE clears > it all out. Thanks. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:256641 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4

