Or.. you could set breakpoints like ferretrunner says. But I've found that when tracking recursion problems down on a form, the act of debugging causes problems as focus changes from your program to the VB IDE, and back again.
You can minimize this problem by running on a PC that has dual monitors (VB on one, program under test on the other one). Or you instrument your code like I suggested earlier.
Chip H.
If you want to get the best response to a question, please check out FAQ222-2244 first