Alan,
If I read your question correctly, I would do it like this
1. fuseaction=enteruser
[original form for data entry]
2. fuseaction=previewuser
[dsp_preview.cfm]
3.fuseaction=adduser
[act_adduser.cfm]
It makes more sense to me this way and will probably make it easier for the
code maintainer at a later date. Also, if you decided to take out the
preview step - 'cause your users are sooo smart and capable ;) - then you
could point your entry form at the adduser fuseaction and easily eliminate
the preview action. No preview code entangled with the adduser code.
Kevin
--------------------------
Kevin Marshall
Certified ColdFusion Developer
eCalton.com, Inc.
Vero Beach, FL
www.ecalton.com
[EMAIL PROTECTED]
561.569.4500
"Alan Walker"
<alanwalker@consu To: Fusebox
<[EMAIL PROTECTED]>
ltant.com> cc:
Subject: Multiple Fuses in a
Fuseaction
11/11/00 08:24 PM
Please respond to
fusebox
Hello all,
I've been developing Cold Fusion for about 18 months now and I'm trying to
understand the Fusebox methodology. I'm putting together my first Fusebox
app and I'm confused about using multiple fuses within a fuseaction. In
the
user registration process, I have the users preview their data before
committing to the db. I have the original form go to the adduser
fuseaction. This is where I am getting confused, the adduser fuseaction
will send it to dsp_preview.cfm file, the preview page with a hidden form
containing all their data. Do I have to create another fuseaction,
previewuser for example, that then calls the act_adduser.cfm file or is
there a way to keep the entire process within the adduser fuseaction?
Still trying to clear the fog.
Thanks for your help.
Alan
------------------------------------------------------------------------------
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.
