>I'm running into something really weird and not sure where to go with it. I've spent the last couple of days tracking down weird behavior in a form and finally figured out that it boils down to a WAIT WINDOW in a form resulting in the form's Activate code firing, which has some undesired side effects. I've confirmed that it really is the WAIT WINDOW (which has a TIMEOUT clause) and that it really is Activate firing, both with my own debugging code and with the Event Tracker.
>
>What makes this so strange is that I can't replicate the issue in a basic form. That is, if I just create a form and put a DEBUGOUT command in Activate and then either set up a button with WAIT WINDOW 'something' TIMEOUT 1 or put that code in the form's Click, when I run the code and click either the button or the form, the WAIT WINDOW appears, but Activate doesn't fire. Confirmed both with my DebugOut and with the Event Tracker. Tried both modal and modeless forms, though my real form is modeless.
>
>I also tried testing with a form based on the base form class from this project and can't replicate there either. It would take quite a bit of work to create a test form based on the same class as the form that's giving me trouble. However, I just tested with a simpler form that's based on the same class in that case, the same WAIT WINDOW (albeit run from a slightly different path) doesn't result in Activate firing. So what could be happening in a particular form that would lead to Activate firing after a WAIT WINDOW?
>
>Obviously, I can solve my issue by removing the WAIT WINDOW, but I'd really like to understand what's going on. Beyond that, this is embedded deep inside an application in the process of conversion from FPW to VFP, and it uses WAIT WINDOWs extensively to communicate with users, so removing this particular message is a UI issue (and replacing all WAIT WINDOWs with a combination of status bar messages and messageboxes is a non-starter at this time).
>
>Anybody have any ideas what might be going on here?

What are the differences between "a simpler form that's based on the same class" and the one with the issue?

Any BINDEVENT(), _Access/_Assign or similar in play?