There is a ClientTimeOut feature in progress. We have ours in the
progress\bin\progress.ini in the startup section. It looks like this, it's
the fifth line. We don't have ours in the registry and it works fine. You
may need to pop it in the registry and run the Progress Network Client
Install on each workstation if it doesn't want to work.
[Startup]
V6Display=no
;ImmediateDisplay=yes
;MultitaskingInterval=100
ClientTimeOut=15
DefaultFont=MS Sans Serif, size=8
DefaultFixedFont=Courier New, size=8
DLC=d:\EPICOR\PROGRESS
Use-3D-Size=Yes
PROBUILD=d:\EPICOR\PROGRESS\PROBUILD
PROPATH=.,d:\EPICOR\PROGRESS\gui,d:\EPICOR\PROGRESS,d:\EPICOR\PROGRESS\bin,d
:\EPICOR\PROGRESS\PROBUILD\EUCAPP\EUC.PL,d:\EPICOR\PROGRESS\PROBUILD\EUCAPP
*****************************************************************
The following is a knowledge base entry for the Clienttimeout feature from
progress.
KnowledgeBase number: 18415
Creation Date: 11/25/98
Modified Date: 11/25/98
Modified Date: 12/06/99
This document applies to: ClientTimeout Parameter
Version and Release Number: 7.3B + NT database server products
Summary: In version 7.3B, a new startup parameter, ClientTimeout, was
introduced. This parameter allows the server process to determine
whether a client has been inactive for a specified period of time, and
if so, the server disconnects the client and backs out any related
active transactions. The parameter does not work as currently
documented, however the functionality is there. This is not available
as an online startup parameter. There is a doc bug entered for 9.0B
and earlier releases. There is also an enhancement request submitted
to make this a startup parameter that will be accepted at the command
line.
Step by step details:
The parameter uses the following syntax:
Clienttimeout=n
where n is the number of minutes a client can be idle before the
server disconnects it.
This Clienttimeout parameter can be put into the registry in one of
the following keys, by default this key will not exist so will need to
be created.
HKEY_CURRENT_USER\SOFTWARE\PSC\PROGRESS\<VERSION>\STARTUP
or
HKEY_LOCAL_MACHINE\SOFTWARE\PSC\PROGRESS\<VERSION>\STARTUP
where <version> is the current version (e.g. 8.3A).
Regardless of how you start the server, command line or ProControl,
the ClientTimeout parameter can be set in the progress.ini file or the
registry. If the registry key exists, the progress.ini file is
ignored. This means that if the key exists and you want the
ClientTimeout functionality it must be set in the registry. If you
want to use a progress.ini file to set this parameter then you must
remove the registry key. As of version 8.0 of Progress, which
introduced the use of the registry with Progress, and the ini2reg
conversion tool, the registry entries take precedence over the
contents of the ini file.
The -clienttimeout server startup parameter is planned for a future
commercial release, although version and date are not confirmed as
yet. When introduced the existing ClientTimeout parameter will no
longer be valid in the registry or the progress.ini file.
-----Original Message-----
From:
lgourley@... [mailto:
lgourley@...]
Sent: Thursday, April 12, 2001 8:40 AM
To:
vantage@yahoogroups.com
Subject: [Vantage] Idle time kickoff?
Hi all,
Is there such a thing as a setting to boot people out of vantage if
their idle time is too long? We are running out of licenses and
have found that people are logging in and then just keeping vantage
open all day till they logout. After numerous warnings to these
people they still keep on doing it. Any ideas?
Lucas Gourley
Grimm Brothers Plastics
To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please go to:
http://groups.yahoo.com/group/vantage/files/. Note: You must have already
linked your email address to a yahoo id to enable access.
Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/