Al,

>I would also like to see information on the practical use of DEBUGOUT and methods for logging event firing sequences. BTW are there any good articles and/or FAQs here on any debugging topics?

I never use WAIT WINDOW anymore, I use DEBUGOUT instead.

1) You can use the window to scroll through a sequence of events. The contents of the window can be copied to the clipboard so you can compare two different program runs.

2) There is a little UDF over on my website to build strings out of multiple arguments. I wrote it because debugout can only output one expression at a time.

3) If you want to trace methods that aren't events you can seed debugout program() lines into the methods of interest.

4) ACTIVATE WINDOW "DEBUG OUTPUT" can be used in your code to open up the window prior to doing any debugout commands.

5) You can document differences or what you did at any given moment by doing a debugout in the command window while you are testing.