If you have an event in a .w that has logic to close the window, the last event is being carried over to the .NET window behind it. Basically, if you handle the DEFAULT-ACTION trigger of the Progress browser and has a logic to close the .w at that point, the DEFAULT-ACTION event (which is a double-click) is still active and the .NET window will catch it too. The same thing is true for KeyUp when you have a logic that closes the window (.w) inside the KeyDown event.

Has anyone noticed this?