http://forums.method.me/cs/forums/13.aspxAsk technical support questions, how do I? Questions... Or anything else you want to know from the Method Team and other Method users.enCommunityServer 2007.1 SP2 (Build: 31113.47)http://forums.method.me/cs/forums/thread/14405.aspxMon, 05 Nov 2012 23:01:34 GMT3393c1ec-311b-4812-96cb-ad8c611bba4f:14405Method_Ashur0http://forums.method.me/cs/forums/thread/14405.aspxhttp://forums.method.me/cs/forums/commentrss.aspx?SectionID=13&PostID=14405<p>Hi Blake C,</p> <p><span style="overflow:hidden;"></span></p> <div>Debug Tracing doesn&#39;t show any errors a user would receive based on the actions being performed, instead it was designed to show all the values held from each of the actions (what is assigned and when), i.e. Assign Value to Action Result, Character Function, Retrieve Value from Table, etc. So you as the customizer would be able to see where a value would not be assigned correctly and work from there. Therefore your INSERT action wouldn&#39;t show up using the Debug Tracing option. Regarding your error message being &quot;swallowed up&quot;, I&#39;m guessing the debug message comes up first since all conditions are met for it to display, cancelling out any messages which would come after it. If there was an issue before the debug message was to display then the action error message would show but not the debug tracing one.</div> <p><span style="overflow:hidden;"></span></p> <div>- Ashur</div> <div></div> <div></div>http://forums.method.me/cs/forums/thread/14377.aspxFri, 02 Nov 2012 19:42:29 GMT3393c1ec-311b-4812-96cb-ad8c611bba4f:14377Blake C0http://forums.method.me/cs/forums/thread/14377.aspxhttp://forums.method.me/cs/forums/commentrss.aspx?SectionID=13&PostID=14377<p><span id="mce_0_start" style="overflow:hidden;">I&#39;ve used Debug Tracing more this week as I&#39;ve been creating more cust<span id="mce_1_start" style="overflow:hidden;"></span>omized,&nbsp;detailed Actions. While doing so, I noticed the tracing results just ended at a point I was expecting an INSERT action. I spent a lot of time checking the Actions on the screen to make sure things seemed good. Finally, I turned debug tracing OFF, then tried the screen again and immediately an error popped up regarding a problem with my table INSERT.</span></p> <p><span id="mce_0_start" style="overflow:hidden;"></span>So just a lesson to anyone that might search this forum for debug tracing help...errors are &quot;swallowed up&quot; when debug tracing is ON. So when developing/testing/debugging a screen, be sure to try out your screens with both Debug Tracing ON and OFF in order to get the whole picture.</p> <p>Hope this helps.</p>