>>>That's what I had in mind - a MOUSE command? Have a blank space that we can click without actually doing anything.
>>
>>I haven't worked with passing messages from Fox to other Windows apps. Maybe you have to invoke the TS client program from within Fox so you can grab a handle to it - I don't know if that's necessary or not. As for the actual Windows message passed, could be a mouse move/event of some kind, pressing the Shift key etc. (?)
>
>Oooops... I was off by one hop :). Don't know what could be done to do this, because from what I know, the app is running on the server, and the client has no clue on what's going on there - it only receives the messages to display stuff, maybe play a sound or print a document but that's it. And it checks for activity for itself, without any consideration of what app may be running in the session.
>
>There's only the possibility to set the timeout (server side, if I'm right) to max, which should be several hours, maybe as many as 20.

On the server side, that's true, I don't know of any way to reset the timeout counter from an app within the session - kind of defeats its purpose. But the client process on the client computer also sends keystrokes, mouse moves etc. back to the session on the TS - I'm thinking that's what counts as "activity". So, if the client process could be "automated" somehow, causing it to send keystroke/mouse traffic back to the TS session, that should reset the inactivity timer.