Somehow this thread seems to have gotten split. I mentioned elsewhere that you can remove this behavior setting "Max Pooled Statements" in the advanced properties on your datasource to 0. Then you can run your query again and it will not use the cached query statement. I actually ran into this way back when I was testing Joe Rinehart's Arf! project ( http://www.remotesynthesis.com/blog/index.cfm/2005/12/2/Queryparam-Issue-and-Arf) - sorry I mistated on the other post that I thought it was Reactor.
Every solution to this problem that I am aware of requires your personal intervention 1) modify the query somehow...for instance you can just add an extraneous space, and rerun 2) set the max pooled statement, rerun and then reset max pooled statements. This is why I recommend (as I believe others have) that you don't use Select *. This still means that you must intervene and modify the query when you change columns, but you are no worse off than before (and not dealing with hard to debug issues like this), and you get the benefit of the performance increase from your rdms by not using select *. -- - Brian Rinaldi blog - http://www.remotesynthesis.com/blog CF Open Source List - http://www.remotesynthesis.com/cfopensourcelist Boston CFUG - http://www.bostoncfug.org ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:254598 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
