Use the REQUEST scope. REQUEST is only valid from one form to the next
form, so the information should carry over.
Many thanks to the FuseBox conference last weekend that taught me this
trick.
Bobby Nichols
===================================================================
Center for Engineering & Environmental Tech. Research Triangle Institute
(919) 541-8009 Voice (919) 541-6936
Fax
<[EMAIL PROTECTED]> E-mail
-----Original Message-----
From: Martin Cadirola [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 22, 2000 11:49 am
To: Fusebox
Subject: Building dynamic queries & cflocation
Hello!
I've been recently doing fusebox and I'd like to know your experience
with the following coding task.
Let's say you perform a query to find an email on a db. Then you need to
look at the recordcount variable to decide whether you go to option 1
(success) or 2 (failure).
I separate the query and the decision code in two different files:
qry_GetUserEmail, act_IsEmailIn. To be able to go to either decisions, I
use <cflocation>. Let's say one of the options of the act_IsEmailIn
requires usage of the same query variable created on qry_GetUserEmail.
Of course, if I use cflocation in between them, the variable will be
gone.
My question is, should I use sessions variables to pass queries within
the same circuit app? How do keep the same scope when dealing with
conditional statements?
Any suggestions are greatly appreciated.
Thanks !
Mart�n Cadirola
----------------------------------------------------------------------------
--
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebarRsts&bodyRsts/fusebox or send a message
to [EMAIL PROTECTED] with 'unsubscribe' in the body.
