Hi Chris,
I'm not sure if I've managed to express our problem properly.
What we are struggling with is that we have a Powerbuilder process that one has published on RDP,
and when then starts other processes (ex. Word, excel ..) on the machine that this pb prosess is published on
it is often one cannot manage to get back focus on the powerbuilder application again.
Although one clicks on the icon on the process line, the focus stays on oen of the others.
One had to minimize all other processes for the powerbuilder process to become active again.
So it seems that powerbuilder fail to become the active process without everyone else being minimized.
You suggest getfocus () and setfocus (), but I am unsure I have explained too poorly and that you may have understood me so that it is the powerbuilder process that starts the rdp process and not that it is the published rdp process.
If it turns out that I am wrong and that you have not misunderstood me, then I am still unsure where to enter Getfocus and Setfocus.
best regards
Ivan.
Yes, RDT (formerly "terminal Services") by MS is not officially supported by Appeon PB. Most Apps will work OK but do experience odd things like you describe, focus issues and lack of mouse wheel scrolling (jut to name a few). I am not sure what else to advise you here to escape your RDT issue.
Maybe other RDT users can "chime in" here if they have developed any "workarounds" or have tips / insights when using RDT.
Regards ... Chris
Hi Chris,
Thank you so much for your informational responses. I think my solution now has to be in dialogue with operation. We must look at opportunities to change the use of the system. Thus, we must consider how we can get away from the RDP (MS-Terminal) service using the Powerbuilde application.
I also think to leave the thread open a little longer in the hope that there may be someone out there who has been in the same problem and managed to create a solution that works.
best regards
Ivan.