Hi
Currently have a 9.1D app that calls an external .NET exe to show a report. We call the external exe using the CreateProcessA API call which works fine. The problem is on returning back to the progress app the window with the button-widget that called the external EXE is not always the window given focus.
I have tried all the Progress Knowledge base solutions such as
Assigning current-window and the win32 api call setforegroundwindow but they still don't gaurantee that the correct window will be in the foreground.
Example MenuWindow calls POwindow
Powindow calls .NET EXE
On exit of .NET EXE foreground window could be the menuwindow even if the focus has been given to the POwindow.
Anybody with any ideas?
Thanks
Currently have a 9.1D app that calls an external .NET exe to show a report. We call the external exe using the CreateProcessA API call which works fine. The problem is on returning back to the progress app the window with the button-widget that called the external EXE is not always the window given focus.
I have tried all the Progress Knowledge base solutions such as
Assigning current-window and the win32 api call setforegroundwindow but they still don't gaurantee that the correct window will be in the foreground.
Example MenuWindow calls POwindow
Powindow calls .NET EXE
On exit of .NET EXE foreground window could be the menuwindow even if the focus has been given to the POwindow.
Anybody with any ideas?
Thanks