1. Roland Smith
  2. PowerBuilder
  3. Sunday, 22 October 2017 17:06 PM UTC

The problem was first discovered in a PB10 app but I verified it happens in PB 2017. I am on Windows 10.

The main window of the app is MDIHelp. Clicking a button opens a response window. Clicking a button on the response window opens another response window.

If I close the second response window by clicking the X button in the upper right corner, the first response window is moved behind the main window and becomes unresponsive.


Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 23 October 2017 12:39 PM UTC
  2. PowerBuilder
  3. # 1

Hi Roland;

   My framework allows response withing response within response windows to be opened from an active MDI frame window in behind. Try as I might, there is no way that I can close the 1st or 2nd response window without closing the last open opened first, then the 2nd, 1st and then back to the MDI window. Thus, there was no way in my architecture that you can close a primary response window before the secondary response. I tried unsuccessfully to recreate your situation with my test applications over the weekend.

  Sounds to me that you have a unique situation in the way you are either handling response dialogues and/or the settings you use in your response window properties. I would like to suggest that your create a test case and upload this to the support system to review further.

Regards ... Chris

There are no comments made yet.
George Mikhailovsky Accepted Answer Pending Moderation
  1. Sunday, 22 October 2017 22:35 PM UTC
  2. PowerBuilder
  3. # 2

Dear Ronald,

I believe that opening response window from another response window is not a good idea. Response window is an application modal window, and a user is force to response in some way and close it before doing something else in the application. So, usually response window shouldn't have control menu (cross in the right upper corner) at all. 

I would recommend to make the first of your windows popup one. This would solve your problem.

Best regards,


  1. Roland Smith
  2. Sunday, 22 October 2017 23:12 PM UTC
Clicking the Close button I placed on the window works as expected, the problem only occurs clicking the X button on the title bar.

I unchecked the ControlMenu property and that solved it.

  1. Helpful
  1. Miguel Leeuwe
  2. Wednesday, 25 October 2017 04:48 AM UTC
Hi Roland, just out of curiosity: What happens if you do ALT+F4 to close that window, does it still work correctly?

Did I understand well that you open the first response straight from the mdi frame window itself? So there's no sheet from where you open it? If so, you could try to have an invisible sheet window and open the first response window from that one. Think I did something like that long long time ago, so not sure if it would work.

Just an idea, but I have the feeling that this incorrect behaviour in windows 8 and 10 (now also windows 7? since they push back all the "improvements") might have something to do with windows "not wanting to bother users with windows popping up (unless it's windows itself bothering you)". You can see that, when for example you want to show an address list for email when using OLE and outlook: The icon which represents the window of the address book "stays flashing" in the task bar and you have to first notice that and then click on it to see the window (the only way to get around that one is to use mapi for your addressbook and ole for the rest).

My wild guess is that maybe windows does not interfere as much if your response window has no red-cross-control to close it. Who knows how long this will still work.

Kind regards,


  1. Helpful
There are no comments made yet.
  • Page :
  • 1

There are no replies made for this question yet.
However, you are not allowed to reply to this question.