I finally got a chance to work more on this issue.  I have identified that the issue is related to the PFC window preference service (resize and position).  Specifically, in the pfc_n_cst_winsvr object (pfcwnsrv.pbl).  When the of_SetRequester function is run, it assigns the window to "w_master".  I'm guessing this assignment removes the icon that the opening window has?  Not quite sure the logic on that, but when I don't call that function the icon will correctly appear in the taskbar as expected.

This is the code which is causing this to happen: iw_requestor = aw_requestor

In my window I put this in the pfc_preopen event: 

// save the window size and position
this.of_SetPreference(TRUE)

Any thoughts on what could done to avoid this behavior?  The PFC library hasn't been modified for that object, so I'm not sure why this is happening.  Maybe it's always had this behavior, but it's never been an issue until we had remote users who noticed it (due to the speed of the program opening up).

Hi, Lisa -

I can't say with definite certainty, but I believe that the application's icon in the Windows taskbar does not appear until application's window (an MDI frame window, I surmise in your case) is displayed.

Does your application utilize a "splash" window? I know the PFC provides one. If not, this may be something you wish to investigate.

The commercial app I help support is also a PFC-based PB application utilizing an MDI frame as its main window. We have tailored the startup/open process to minimize any delay prior to the opening of the frame window. You did not elaborate on what your app does that delays it from opening quickly, so it's impossible for me to provide you with much useful advise. However, listed below are some of the tips/techniques we use. Maybe one or more will be helpful.

1. We use a splash window. It gets opened immediately. We've tweaked the amount of time it is visible so that it disappears as soon as the MDI frame window opens.

2. The MDI frame opens quickly, prior to database login, then the modal login (response) window is immediately opened. If the user login process ultimately fails, the MDI frame window and application closes. If the user does not successfully login with 60 seconds, the login window, the frame and application are closed. Using a modal response window for the login keeps the user from being able to interact with the frame window and menu.

3. After a successful login, customization of the frame menu, library search path, configuration and customization options, etc. are performed. The hourglass cursor displays during this time, and the MicroHelp area gets updated as each step progresses to let the user know the app is working.

Best regards, John

Never heard of this before.  Can you reproduce problem on multiple machines to verify it isn't your particular Windows install that is corrupted?  Also, what version of PowerBuilder are you using?

Yes, a different computer had the same issue.  I have attached "before" and "after" screenshots.  You can see the open program behind the browser and no icon in the taskbar.  After I clicked on the program the icon showed up.

We are using PB 2022 R3.  I tried some of our old programs which are in PB 17 and the issue was there also.  Given that you have never heard of this, perhaps it's something in our code.  We are using the PFC libraries.  The reason I probably notice it now is because I am working remote and our programs take longer to load through our VPN.

Hi Lisa;

  I am running native W10 & W11 O/S for many years and in W11 in particular since PB 2022 GA (1st PB release to officially support W11 and I can certainly say that I have never seen that behaviour before.  FYI :  https://docs.appeon.com/pb/whats_new/Updated_system_requirements.html

  As Armeen stated, please open a support ticket if you can recreate a simple test case & detailed steps to recreate this phenomenon.

PS: Did you also upgrade the PFC framework version to 2022 as well when you migrated your App(s) to PB 2022 R3?

Regards .. Chris

We did update the PFC libraries.  In previous years used PFC libraries which I migrated from an older version (for 17 and 19, because I had modifications to the code) but for PB 2022 I did download the published libraries and made my changes to them.  That was within the past month or so.  I'll have to start digging in my code, and also creating a simple test app.  There must be something hiding in our code which is causing this issue.  We do have some code which will check to see if the program is already running and stop the program if it is (so there are not duplicate programs running) but I commented out that code and I still had the issue.