Perhaps you do a cfset above the second proc
<cfset request.procname = "course" & i & "Apply" & ceuPref.strCme>
Then reference that in the tag
<cfprocresult name="#request.procname#">
the thing that's popping out to me is your "in" params
<cfprocparam type="In"
cfsqltype="CF_SQL_DATE"
variable="fromDate"
value="#getCourse#i#.CREDITDESIGNATIONFROM#">
<cfprocparam type="In"
cfsqltype="CF_SQL_DATE"
variable="toDate"
value="#getCourse#i#.CREDITDESIGNATIONTO#">
something looks very wrong here. Like you almost want to dynamically evaluate a
queryname
#eval("getCourse" & i & ".CREDITDESIGNATIONTO")#
(BTW, the proc result of the previous proc is "course#i#", which might also be
at issue with defining your second related proc)
The bigger thing I'm wondering is why you really require two separate procs. In
most of the cases of this that I have seen, two procs could be written as one
through proper usage of joins, and save you some overhead (and headaches).
Steve 'Cutter' Blades
Adobe Community Professional
Adobe Certified Expert
Advanced Macromedia ColdFusion MX 7 Developer
____________
http://cutterscrossing.com
Co-Author "Learning Ext JS 3.2" Packt Publishing 2010
https://www.packtpub.com/learning-ext-js-3-2-for-building-dynamic-desktop-style-user-interfaces/book
"The best way to predict the future is to help create it"
On 4/17/2014 11:36 AM, Torrent Girl wrote:
> <cfprocresult name="course#i#Apply#ceuPref.strCme#">
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Order the Adobe Coldfusion Anthology now!
http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion
Archive:
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:358345
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
