Thanks everyone, You were all correct - god help me I was actually focusing on the error CF gave me, trusting that alone. Go figure. What a rotten thing to do! :)
A different value was the culprit, and the suggestion below absolutely applies. Thank you all so much -- this is what happens when we get tired, and I always appreciate the fresh perspective of the community during such times! > It's a bit more code, but if you switch to having a cfargument tag for > each parameter and enforce the type there, you can pass in your > struct as an argument collection. You'll get a more meaningful error > that way. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:334851 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
