IBF processes asynchronously
I like to learn the hard way. You can tell me something a thousand times but I guess I simply like to here/see it from testers/users...
Oh well... here is another hard-learned lesson I will share.
IBF process operations asynchronously.
Asynchronous
\A*syn"chro*nous\, a. [Gr. ? not + synchronous.] Not simultaneous; not concurrent in time; -- opposed to synchronous.
Source: Webster's Revised Unabridged Dictionary, © 1996, 1998 MICRA, Inc.
Yep... I fumbled on this one where I had an IBF region that redrew its information based on the results set by the update operations of another IBF region. It didn't work because the code wasn't "managing" the transaction process. What happened was the update went thru, but the redraw was not guarenteed to fire after the update, so the old data was captured and displayed, not the new. Shame! Shame!
Note to self: in the asynchronous world that IBF lives in, you have to manage how and when your events get executed. IBF cannot do it for you.