Thanks for the help. I am coming into an application that is already deployed. I'm here to fix bugs and add functionality. I am in the process of converting a lot of stuff to a few session scoped structures.
The scoping going on in the frameset and frames is a little funky. My first goal is to get all of the variables passed and scoped properly. And if I had thought about how the thing was working, I would have been able to answer my question. Doh! The form thing is very slick, though. Thanks again! -----Original Message----- From: Bryan Love [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 01, 2001 8:43 PM To: CF-Talk Subject: RE: Frames and variable scoping Keep in mind that variables are processed server side while the frameset tags are processed client side. That means that ONLY the page you call with the form action can see the form variables - in this case that page will likely have the FRAMESET tags and nothing else. Once that page is served up the browser initiates requests for the frame sources - by this time your form variables are gone. Your only option here is to generate the frame tags on the fly using CF and put the form variables in the url string for the SRC attribute. This way when the browser makes the request for the frame source your variables will be passed in again through the url scope. You could also store the variables in a persistant scope, but it's probably not the best idea. If you do decide to do this there is one very easy way to do it: <cfset session.theForm = form> (this works because form is actually a struct pointer which is getting copied into the session.theForm variable) then you can access the variables later like this #session.theForm.fieldName# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
