Here's my two cents. I rue the day they took away the server.sy# file. If I had to do midnight maintenance, it was easy to bump users off. The problem was, as I remember, that there were other issues with the server.sy# file that caused more problems than they were worth. The timer file probably won't work if the user is in a form. The only thing that works is the "SET TIMEOUT" command, and that does work at the main menu of an application. Haven't tried it in 7.0 yet, but works great in 6.5++. There are no good solutions that I know of. Maybe some other users on this list have an alternative.
Bob C.
William Stacy <[EMAIL PROTECTED]> on 09/23/2003 02:38:43 PM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED] (RBASE-L Mailing List)
cc: (bcc: Bob Castanaro/BCH)
Subject: [RBASE-L] - Re: Managing Multiple Connections (Users) in
RBWIN6.5++
I'm thinking the same thing and am probably just going to create a
little timer file that after an interval of inactivity, say 5 minutes,
will exit them from my app. Alternatively, you can use the screen saver
function of windows to blank the screen after an interval, and require a
password to use the computer at all. The latter approach will leave the
user connected to the database, but that should not be a problem unless
someone wants to take the server down for maintenance or nightly shut down.
bill
J. Stephen Wills wrote:
> Folks, as I'll be facing this one pretty soon, is there any generally
> good approach to managing multiple connections (users)? I mean, I
> know I'm gonna' have users who walk away "whenever" and leave their
> app' up and therefore connected. Is there a way to manage f/this type
> of thing, to gracefully log 'em off? What about some other user
> walking up and just re-booting while the (still) connected user went
> out to smoke/eat/etc w/say, a header record saved but not the detail
> records, or something similarly risky? I know it's impossible to
> regulate the user(s) behaviors, but what would/could the risk to the
> data and the database and what is recommended to mitigate the impact.
>
> Thanks,
> Steve in Memphis
|
I'm thinking the same thing and am probably just going to create a
little timer file that after an interval of inactivity, say 5 minutes,
will exit them from my app. Alternatively, you can use the screen
saver function of windows to blank the screen after an interval, and
require a password to use the computer at all. The latter approach
will leave the user connected to the database, but that should not be a
problem unless someone wants to take the server down for maintenance or
nightly shut down. bill J. Stephen Wills wrote:
|
