I'm thinking there's gotta be one last "desperation call" to a stored
procedure with the person's key in an attempt to "unlock this dude's
record" but of course, if you've lost connection to the database (and it
can't reconnect), I'm guessing that user would have to call the HelpDesk
to say "hey, I can't get back in after this crash."
Stephen Weeks -- let's hear the answer! :-)
On 2015-12-09 17:02, Mike Copeland wrote:
Sounds reasonable, but how does the "/...in the event of a crash the
lock is automatically removed./" part work?
Thanks for any enlightenment.
Mike Copeland
[email protected] wrote:
On 2015-09-17 03:32, Stephen Weeks wrote:
I have a user table and when the user logs in it puts a lock on
his/her
record and removes it when the user exits the syetem, in the event of
a
crash the lock is automatically removed.
That seems like the most logical way to easily accomplish the "only
allow unique logins" scenario. Thanks for the tip.
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
