There's two sides to this. 1) doing something like this: <cfset iMatch = sValue.indexOf('c')>
That's leveraging the fact that a CF string is actually a Java string, and using a standard Java string method upon it. 2) <cfset qRecords1.populate(qRecords2)> That's leveraging the fact that a CF query is actually a Java class, and comes with some *undocumented* methods. However it's something the Allaire / Macromedia / Adobe bods cooked up for their own benefit, not ours. The former is perfectly fine. The latter is "use at your own risk". I asked on some beta programme a while ago (it might have been 6.1, I can't remember), if they could document and "officialize" the underlying Java methods of the internal CFMX Java classes. The response was "no way". Pity. -- Adam --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~----------~----~----~----~------~----~------~--~---