> Across the board yesterday , I read "avoid evaluate", but I could not > find any guidelines on when it "must" be used.
The only occasions I've found I've needed to use it is when the SCOPE of the variable is dynamic too (don't ask). > form["MyRadio" & IndexNo] > I have not tested this yet, as it seems this is an MX feature and I am > on CF 5 for the next week or so. CF5 doesn't expose all its scopes as structs, so it's not always possible to use struct notation in CF5, which is a shame. In this case... use evaluate(). This is a pity because evaluate() is even more of a pig in CF5 than it is in CFMX. If possible... re-code so as to not have dynamic variables like that (not always possible, I know, but *try* ;-) > However, I am dealing with a situation shared by Bec Gorton where I am > reading the column names from the database. queryName[stringHoldingColumnName][rowNumber] Naturally 'stringHoldingColumn' name can be any expression one likes, as long as it results in a string. So it can be a function return, a concatentation of multiple strings, whatever. -- Adam --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
