http://blogs.msdn.com/microsoft_dynamics_nav_sustained_engineering/archive/2008/06/29/the-random-events.aspxSome years ago I was dealing with an issue that was driving me crazy and it took many hours to figure out what was wrong with the code. It was until I was explaining my findings to a colleague (don't you solve lots of things this way?) that it hit me,en-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/microsoft_dynamics_nav_sustained_engineering/archive/2008/06/29/the-random-events.aspx#8669353Mon, 30 Jun 2008 04:02:12 GMT91d46819-8472-40ad-a661-2c78acb4018c:8669353AGATADEV &raquo; The random events<p>PingBack from <a rel="nofollow" target="_new" href="http://agatadev.com/?p=8373">http://agatadev.com/?p=8373</a></p> http://blogs.msdn.com/microsoft_dynamics_nav_sustained_engineering/archive/2008/06/29/the-random-events.aspx#8671072Mon, 30 Jun 2008 13:41:50 GMT91d46819-8472-40ad-a661-2c78acb4018c:8671072Kine<p>Yes, assuming something when programming is bad idea... :-) mainly in connection with time. (I assume that this will end before this etc.). You must be sure that it will go as you wish... 8-)</p> <p>Kine</p> http://blogs.msdn.com/microsoft_dynamics_nav_sustained_engineering/archive/2008/06/29/the-random-events.aspx#8740097Wed, 16 Jul 2008 23:18:26 GMT91d46819-8472-40ad-a661-2c78acb4018c:8740097jtorres<p>Indeed, wrong assumptions are costly.</p> <p>Of course, we can assume that the Global variables will stay with their value after the call back (in a single instance code unit). The problem is assuming which call backs (events) are called first.</p> <p>/Jorge</p>