>Hi Jon,
>
>>There are WAIT commands in the form, but they're all cleared.
>
>If there's a WAIT command, the mouse down will clear it, too. This can make it impossible to see a wait window, at all. All you notice is that the MouseDown event is ignored.

I realize I wasn't clear on this. The WAIT commands have NOWAIT NOCLEAR options with them, so there is never any pausing going on.

>> Another thing to point out is that the necessary double-click to activate the other page only happens one time.
>
>This sounds like there's some code that only runs the first time and either moves the focus or catches the mouse events. Have you tried SET COVERAGE to find out which lines are executed when you need to double click vs. when a single click is sufficient?

I did try the coverage profiler and event tracking. The coverage did not show me any valuable information in terms of when the double-click is necessary to switch pages. It just shows the click, deactivate, and activate. The event tracking showed something interesting: The first click on the other page that doesn't produce results actually shows up as MouseMove events with the left button held down, followed by a MouseUp. It seems like the mystery is why the MouseDown event isn't firing that first time.