Could anyone provide an answer to a general question...
If a session is not closed cleanly, by that I mean if the process is terminated via the task list, or if a session times out from the server and is automatically closed I end up not being able to re-open the same named session by program control, although I can open the session up manually.
Via program control the check to see if a particular session exists will return true. This "flag" seems to be embedded within the Extra! environment and not Windows as it doesn't appear on the Windows task list, and as I said I can open up the session manually. The only way I can re-open the same named session without re-booting the PC is to close EVERY Extra! session, which presumably releases the "flag". The session can then be re-opened via program control - although that kind off defeats the object !!
Is there a way round this, or has anyone else had a similiar problem ?
Your comments would be welcome...
Thanks.
If a session is not closed cleanly, by that I mean if the process is terminated via the task list, or if a session times out from the server and is automatically closed I end up not being able to re-open the same named session by program control, although I can open the session up manually.
Via program control the check to see if a particular session exists will return true. This "flag" seems to be embedded within the Extra! environment and not Windows as it doesn't appear on the Windows task list, and as I said I can open up the session manually. The only way I can re-open the same named session without re-booting the PC is to close EVERY Extra! session, which presumably releases the "flag". The session can then be re-opened via program control - although that kind off defeats the object !!
Is there a way round this, or has anyone else had a similiar problem ?
Your comments would be welcome...
Thanks.
