Then the error is because there is no parameter called SelectedOfficeID.
If you remove the cfabort and leave the cfparam it should work to an extent.
You need to check where the SelectedOfficeID is being setup and make sure it
exists before the custom tag call. Maybe wrap the custom tag call in an 

<cfif isdefined("SelectedOfficeID">
        <cf_SelectOffices SelectedOfficeID="#SelectedOfficeID#"
Debug="true">
<cfelse>
        <!--- Gracefully handle error condition --->
</cfif>

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Andrew
Dickinson
Sent: Thursday, 22 January 2004 11:21 AM
To: CFAussie Mailing List
Subject: [cfaussie] RE: custom tag weirdness


> just above the customtag include output the #SelectedOfficeID# value 
> and put an abort after it

> <cfoutput>#SelectedOfficeID#</cfoutput><cfabort>
> <cf_SelectOffices SelectedOfficeID="#SelectedOfficeID#" Debug="true">

This just moves the error up to this line.
I tried adding <cfparam name="SelectedOfficeID" default="0"> above the abort
line, which does as expected, writes a 0 as output without an error.

 
> if the block of code is already in a cfoutput block dont worry about 
> the extra cfoutput around the variable
> 
> I have a suspicion that the SelectedOfficeID var is not there or 
> something is wrong with it

It is the first call on SelectedOfficeID at the top of the program. But
putting in a cfparam either above the tag call or inside it doesn't get
around the error i.e. the tag call falling over.
 
> Also, there should be another part to the error above what you sent

There isn't.
 
> Steve

---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To
unsubscribe send a blank email to [EMAIL PROTECTED]

MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia
http://www.mxdu.com/ + 24-25 February, 2004


---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]

MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia
http://www.mxdu.com/ + 24-25 February, 2004

Reply via email to