|
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 |
- [RBASE-L] - Re: Managing Multiple Connections (Users) inR... J. Stephen Wills

