This is a FYI in case you see the 2570 error appear after upgrading to the latest build. You may have done something dumb, like me.
I have an invoice in one of my vertical applications that has a variable (varchar) vRETURN_POLICY as one of the objects. When I originally designed the report, years ago, the return policy variable was a note data type. When I updated my application to the 5/15 build of V8 the invoice report started posting an error 2570 "data will be truncated" . I tried tracing the section of code that printed the report but the trace would not post the error in single step mode. It would post the error message if I pressed F5 but trace would not point to the line of code that was causing the error. After many hours, I discovered that when I set my VAR vRETURN_POLICY to null prior to printing the report, I was setting it to a note data type rather than a varchar. My defective SET VAR command had been running error free until I upgraded to the 5/15 build. If you start getting 2570 "data will be truncated" errors after updating to build 5/15, this will give you one possible cause. I changed the SET VAR from note to varchar and the error went away. John
