Another way of saying the same thing is that you don't need all the not isDefined() statements in your function. As Peter says, "CF will throw an error if one or more of your arguments are not passed."

Peter J. Farrell wrote:
Here is a example of what I am referring to.
 
<CFFUNCTION NAME="tableSearch" access="remote" returntype="string">
  <CFARGUMENT NAME="searchFor" type="string" required="yes">
  <CFARGUMENT NAME="tableName" type="string" required="yes">
  <CFARGUMENT NAME="fieldToSearch" type="string" required="yes">
  <CFARGUMENT NAME="returnField" type="string" required="yes">
  <CFARGUMENT NAME="searchFieldType" type="string" required="yes">
None of your cfaborts you have defined will be thrown because you have the required attribute set to yes in your cfarguments.  CF will throw an error if one or more of your arguments are not passed.
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email.

CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com).

An archive of the CFCDev list is available at www.mail-archive.com/[email protected]

Reply via email to