I didn't pull that number out of thin air. I counted the errors. The proc was looping over accounting line items and concatenating their invoice codes together for display. Usually there are no more than 5 items to iterate over. Due to some poorly configured pricing setup on a test order, there were 439 items being looped over. The field holding the concatenation was a varchar(255). The average item code was 8 characters long, meaning it would have began erroring after the 32nd item leaving exactly 407 items which would have errored with "string or binary data would be truncated". So I think 400 is a pretty darn good guess.
When I ran the proc in query analyzer I confirmed that was about the number of errors being returned. ~Brad =============================== You're saying this as if you didn't just pull the number 400 out of thin air. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create robust enterprise, web RIAs. Upgrade to ColdFusion 8 and integrate with Adobe Flex http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJP Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:293260 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
