I'm not sure if being in a cfc has anything to do with it... but why are my cfc
functions trying to evaluate street in this case below.
Element STREET is undefined in ARGUMENTS.
cfif isdefined('arguments.street')'#arguments.street#', /cfif
Since the code between the cfif should only run if
I dont know about that but I always use params to predefine my
values and set the default to .
Then check to see if the value is .
On Wed, 08 Dec 2004 09:32:42 -0400, Daniel Farmer [EMAIL PROTECTED] wrote:
I'm not sure if being in a cfc has anything to do with it... but why are my
cfc
Show us the code,
But is it a required argument, if it is not then you might wish to use
the attribute default=
-Original Message-
From: Daniel Farmer [mailto:[EMAIL PROTECTED]
Sent: Thursday, 9 December 2004 12:33 AM
To: CF-Talk
Subject: isdefined function within cfcs?
I'm not sure
On Wed, 08 Dec 2004 09:32:42 -0400, Daniel Farmer [EMAIL PROTECTED] wrote:
I'm not sure if being in a cfc has anything to do with it... but why are my
cfc functions trying to evaluate street in this case below.
Element STREET is undefined in ARGUMENTS.
cfif
4 matches
Mail list logo