Jim Wright wrote: > I have read that not having "set nocount on" can mess up CF's ability
in the past (ie pre MX) you needed it to pump multiple t-sql statements into 1 cfquery. the intermediate resultset counts returned to cf would otherwise confuse it. i forget who exactly figured that out but i think it was a team allaire member, maybe around the time of cf3. it's been a good practice since then (even longer in the sql server world, you'll see it recommended for use in sp that deal w/monster thumping tables all the time). ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:230218 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
