I have a method in place in my application to force users out. It's a
simple tactic I got from these newsgroups where you create a table
with one record called logout, then check that field with a timer on a
form that doesn't close. If it's checked, it starts a forced logout
sequence.
Works fine 99% of the time (unless somebody is in the middle of a
record update and walks away from their computer for several hours,
but that's a different problem). My only real problem with it is when
the database becomes corrupted. Ever since I converted to A03 from A97
and split the database, I've been getting a lot of corruption
(absolutely zero corruption problems with A97 and monolithic DB
structure, again different problem). Anyway, when the DB becomes
corrupted, I cannot even open the database without getting the
'unrecognized DB format, file is corrupted, do you wish to repair it
now?' window that you can't get around, and which does no good because
you can't repair while people are logged in.
I have LDBView, and can use that to help track down 1 or 2 people with
the grudging aid of my helpdesk, but when its 20 people in different
buildings all over the state that is not really practical. The people
who are still logged in when the corruption occurs can use the DB with
no trouble, so I've got to believe there is a way to update that
logout table and force people out.
Anybody know of a way to force a record update to that logout table
without actually being in the corrupted DB itself?
simple tactic I got from these newsgroups where you create a table
with one record called logout, then check that field with a timer on a
form that doesn't close. If it's checked, it starts a forced logout
sequence.
Works fine 99% of the time (unless somebody is in the middle of a
record update and walks away from their computer for several hours,
but that's a different problem). My only real problem with it is when
the database becomes corrupted. Ever since I converted to A03 from A97
and split the database, I've been getting a lot of corruption
(absolutely zero corruption problems with A97 and monolithic DB
structure, again different problem). Anyway, when the DB becomes
corrupted, I cannot even open the database without getting the
'unrecognized DB format, file is corrupted, do you wish to repair it
now?' window that you can't get around, and which does no good because
you can't repair while people are logged in.
I have LDBView, and can use that to help track down 1 or 2 people with
the grudging aid of my helpdesk, but when its 20 people in different
buildings all over the state that is not really practical. The people
who are still logged in when the corruption occurs can use the DB with
no trouble, so I've got to believe there is a way to update that
logout table and force people out.
Anybody know of a way to force a record update to that logout table
without actually being in the corrupted DB itself?
Comment