Cetin,

DEBUGOUT is pretty powerful. I never use WAIT WINDOW or ? anymore during diagnostics like this. It's persistent and scrollable which makes it much more powerful than what we had before. The really cool thing is the window is copy enabled so you can clip out a sequence of events store it to another file and browse two sequences side by side after a code change. It's helped me track down some really oddball object interaction problems. I just wish it easier to type and that it took a list or arguments... I guess a keyboard macro would help and I wrote a udf to handle multiple arguments. The udf is over on my website.

>BTW David thanks for adding "debugout" to my list. It was one of the commands that I never used till today (hmm debugger does more than what I think it could do-now I should upgrade to a 17 or 21" monitor:)