Here's a good message on this that was posted last April. This info should
help you out, it helped me back then.
------Previously posted message--------
Yes there are now 2 ways to do this - one from the server via Progress
directly and one from the client from Mike Podlin.
What follows are his (Mike Podlin's) notes comparing the two. I don't know
if the client
time out utility from Doug williams will work under Progress 8.3 - I thought
I saw a note that it does work but I'm not sure - check with Vantage tech
With all the talk and concerns about timing out idle Vantage session I
thought I would come in today and experiment with it. I spent a bunch of
today trying many different settings and scenarios, watching what happened
at the workstation and server. I tested both the Progress ClientTimeOut
parameter and my ClientTimeOut program. They were both tested against
3.00.631/Progress 8.3A10 and Vantage 4.00.803/Progress 9.0B26 databases.
is running Windows NT 4.0/SP1 the workstations were Windows 98 and Windows
The tests included leaving the computers sit idle from different screens in
Vantage to the extreme measure of turning the PC power off in the middle of
Vantage. [I don't think my hard drives enjoyed that too much with all the
I watched scandisk run after turning the PC back on.]
These are my findings:
The Progress ClientTimeOut parameter:
Its Free (its part of your Progress package).
Is a server based application/control and is difficult for users to get
Will close an idle Vantage session and release the Vantage license.
Will release an orphaned Vantage license caused by an improper shut down of
One setting effects all Vantage sessions.
Vantage Database server must be shut down and restarted to apply changes to
Progress 8.3A - Generates three error messages on the users workstation and
places them into the Progress Procedure editor. (Hitting the enter key
the procedure editor.)
Progress 9.0B - Causes the Win98 workstations to lockup on the third error
message and the machine must be rebooted/reset (shut down was not allowed).
Do not know if this could impact a schemachange process.
My ClientTimeOut application:
Will close an idle Vantage session and release the license.
You can set different time settings per workstation.
Changes can be made simply by editing an INI file and the effects are
next time Vantage is opened (no need to shut down and restart the database).
Generates only one error message at the users workstation.
Also has the ability to prevent more than one Vantage session to be started
run on the workstation.
A smart user can figure out how to change the setting in their INI to
at their workstation.
It is a client side application, if the workstation is improperly shut down
crashes (power off in the middle of something), an orphaned Vantage license
still left open on the server.
Do not know if this could impact a schemachange process, but it can be
disabled before running a schemachange.
This letter is meant to be non-bias and is for your information only.
products work, and after the results from today's experiment I will
implementing both versions here. I will be using my ClientTimeOut program
workstations with their settings at 15 min to 6 hrs (depending on the
user/workstation). The Progress ClientTimeOut parameter will be setup and
enabled at the Server with a registry setting of 480 (8 hrs) to disconnect
close any orphan licenses that were created during the day by a workstation
lockup and/or improper shut down of windows.