Actually I think that would look for a query IN the Attributes scope.  I
think that the original post indicated that only a query name was being
passed in the attributes scope.  If the query itself were being passed
into the tag then this would work but the problem is that "Query" is a
really poor variable name.  If the variable name were "curQuery" then
this would work:


Attributes.curQuery.recordcount


(actually Attributes.Query.recordcount might work - but I think that
"query" is a reserved word.)


If you're on MX any scope can be used in this way so all of the
following would work:


Variables[Attributes.Query].RecordCount


Session[Attributes.Query].RecordCount


Form[Attributes.Query].RecordCount


This[Attributes.Query].RecordCount


And so forth - it really depends on which scope holds the query in
question.


Jim Davis

-----Original Message-----
From: Joe Eugene [mailto:[EMAIL PROTECTED]
Sent: Friday, October 10, 2003 5:07 PM
To: CF-Talk
Subject: Re: evaluate


#Attributes['#Query#'].recordCount#

Joe
  ----- Original Message -----
  From: DURETTE, STEVEN J (AIT)
  To: CF-Talk
  Sent: Friday, October 10, 2003 4:37 PM
  Subject: evaluate

  Hi all,

  I have a lot of files written by another programmer that I now have to
  update.

  Most of these files have things like:     <CFSET myEval =
  evaluate("#Attributes.Query#.RecordCount")>

  I know that evaluate should be avoided, but how would I convert that
to not
  use the evaluate() function?

  Thanks,
  Steve

  _____  


[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to