>>
>>[...] I admit it's a guess that AWindowsEx does not include the path. If I'm wrong on that, please let me know.
>>
>
>No, Mike, it doesn't.
>
>>Beyond that, I would much rather create a cursor than an array because Fox gives so many ways to iterate through a cursor.
>
>

>CREATE CURSOR curHWnds (hWnd I, processId I, visible L)
>APPEND FROM ARRAY hWnds
>

>
>This creates a populated cursor for the last version of the AWindowsEx call I posted.

I really hate to give up, but I see little choice. The goal was to have the launchers be the only icons on the task bar.
Folder1. Launcher1 starts Legacy1 and Hides Icon - actually hides the window
Folder2. Launcher2 starts Legacy2 and hides icon / window.

There are only 2 pinned icons on the desktop - the launchers. Nice.

So user starts Excel or something. Alt+Tab does not show the Legacy apps. Not good.

User clicks Launcher1, which finds hWnd and then showwindow (restore, maximize etc.) App is functional and no Icon on the taskbar. Good
User clicks Launcher2, which finds hWnd and then showwindow (restore, maximize etc.) App menu is non-functional and no Icon on the taskbar. Not good.

Windows does not seem to want to play this way. It is non-standard.

The legacy app can only operate with a single user in a single folder, so to give more functionality, the app was installed in 2 different folders. The launcher is only to get latest version of the exe. A DOS batch file could have done that. If the user pinned DOS batch to the taskbar and that batch started an exe, it would show 2 icons. In this case, the launcher does not release itself and keeps a link to the legacy app, so there is only 1 icon.

MS intent is to have the main exe launched directly. Updates would be a separate thing. Anyone have alternative suggestions?