I wonder if anyone could shed some light on this for me ?
A little question, the answer to which eludes me to date.
(problem experienced in both 6.4 & 6.7 versions)
If I have several Attachmate sessions running concurrently and I call a macro from one of those sessions to, lets say, send some keystrokes to the Active Session (the one that the macro was called from), why does Attachmate send the key strokes to the most recently opened Session ?
I have run many tests, and have even used VB to access the Attachmate Sessions and replicate the function of the macros and every time I have concluded that.....
Set Session = System.ActiveSession
actually equates to....
Set Session = System.LatestSessionToBeOpenedRegardlessOfWhichSessionHasFocus
As, due to a number of operating restrictions, I am not able to "Hard code" the macro to a particular session I have converted all macros into VB applications and have constructed a utility that provides a constant indication of which Attachmate session shelled the VB macro routine.
Has anybody else experienced this problem or found a work around ?
Another thought, would using Session.visible = true force the ActiveSession to report correctly ? - or have I missed something totally obvious !!
Any comments would be most welcome.
Thanks
8Pack
A little question, the answer to which eludes me to date.
(problem experienced in both 6.4 & 6.7 versions)
If I have several Attachmate sessions running concurrently and I call a macro from one of those sessions to, lets say, send some keystrokes to the Active Session (the one that the macro was called from), why does Attachmate send the key strokes to the most recently opened Session ?
I have run many tests, and have even used VB to access the Attachmate Sessions and replicate the function of the macros and every time I have concluded that.....
Set Session = System.ActiveSession
actually equates to....
Set Session = System.LatestSessionToBeOpenedRegardlessOfWhichSessionHasFocus
As, due to a number of operating restrictions, I am not able to "Hard code" the macro to a particular session I have converted all macros into VB applications and have constructed a utility that provides a constant indication of which Attachmate session shelled the VB macro routine.
Has anybody else experienced this problem or found a work around ?
Another thought, would using Session.visible = true force the ActiveSession to report correctly ? - or have I missed something totally obvious !!
Any comments would be most welcome.
Thanks
8Pack