I put the cflocation tag in my fbx_Switch.cfm. It makes the navigation much
easier to keep track of. I hate to have to open up another file just to
confirm where that fuseaction ends up from the user's perspective.
Like so:
<!---@ FuseAction: deleteAnswer --->
<cfcase value="deleteAnswer">
<cfset XFA.onComplete = "polladmin.editPoll">
<cfinclude template = "qry_deleteAnswer.cfm">
<cflocation
url="#self#?fuseaction=#XFA.onComplete#&QuestionID=#attributes.QuestionID#">
</cfcase>
<!--- Fuse: qry_deleteAnswer.cfm --->
<cfquery datasource="#request.dsn#">
DELETE from qp_Answer
WHERE AnswerID = <cfqueryparam value="#attributes.AnswerID#"
cfsqltype="CF_SQL_INTEGER">
</cfquery>
At 06:45 PM 6/20/2002 +0200, you wrote:
>Hi all
>
>How do you handle XFAs in action queries like update and insert. Do you
>use a separate fuse for calling the fuseaction or do you integrate in the
>query-file with the cflocation tag?
>
>I have done it like that:
>
>
><!---@ FuseAction: deleteAnswer --->
> <cfcase value="deleteAnswer">
>
> <cfset XFA.onComplete = "polladmin.editPoll">
> <cfinclude template = "qry_deleteAnswer.cfm">
>
> </cfcase>
>
>
><!--- Fuse: qry_deleteAnswer.cfm --->
>
><cfquery datasource="#request.dsn#">
>DELETE from qp_Answer
>WHERE AnswerID = #attributes.AnswerID#
></cfquery>
>
><cflocation
>url="#self#?fuseaction=#XFA.onComplete#&QuestionID=#attributes.QuestionID#">
>
>
>
>Would it be better to remove XFAs and do it with url_****-fuses. If yes,
>what would the advantages be?
>
>
>Greetings from Switzerland
>
>Urs
==^================================================================
This email was sent to: [email protected]
EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9
Or send an email to: [EMAIL PROTECTED]
T O P I C A -- Register now to manage your mail!
http://www.topica.com/partner/tag02/register
==^================================================================
