I had been using a form.cfm and a confirm.cfm, with the second page
<cfincluding> a processing.cfm page. That way I had broken the logic
down into manageable chunks but I see that using the processing page
as part of the confirm page led to the refresh problem. I think what
you suggest involving three pages is pretty straightforward.
---
Also as I thought more about Critter's suggestion of setting and
checking a session variable on the same process/display.cfm page, I
realized I'd still have to somehow expire that variable to allow an
Administrator to enter and then edit (multiple times if he wanted) the
same record within the same session -- which I don't think Critter's
solution would've supported unless I'm still missing something.
-------------
Regards,
Bob Haroche
O n P o i n t S o l u t i o n s
www.OnPointSolutions.com
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
