[AccessD] forced logout

I was thinking over this just recently.  The problem I have with a pure time
based system is that different computers can have different times.  Normally
this should only be a matter of minutes, but not always.

I saw someone mentioned something like this before and was thinking that one way
would be to create a zero length file in the backend directory.  You could use
different filenames for different purposes:
BESD10.txt - Shutdown in 10 minutes.
BESD5.txt - shutdown in 5 minutes
BESD.txt - immediate shutdown.
BENL.txt - no login allowed

(.txt isn't needed ... Just an illustration)

The reason for this is that most backup programs allow the running of scripts
before and after backup occurs.  And by simply copying a file into the BE
directory and deleting it when done you give the server the ability to centrally
control automated jobs that require users to logout without having to guess how
long such jobs will take.

Just an idea...

Stuart

> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> John W. Colby
> Sent: Wednesday, 11 February, 2004 9:10 AM
> To: Access Developers discussion and problem solving
> Subject: RE: [AccessD] forced logout
>
>
> The reason can be anything.  I need to ensure all users are out of the
> database every night so that compact can occur.  Also I need
> to be able to
> get in and do BE maintenance, modify tables if necessary etc.
>  The users are
> leaving the FE (bound forms) open.
>
> John W. Colby
> www.ColbyConsulting.com
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of
> bruce_bruen at mlc.com.au
> Sent: Tuesday, February 10, 2004 5:11 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] forced logout
>
>
>
>
>
>
> That would depend on the reason for forcing the logout surely?
>
> If the reason is due to a db corruption discovery or to a maintenance
> shutdown then the database should be reopened by an
> administrator manually.
> If OTOH the logout is forced by some business rule then that rule is
> incomplete unless it defines the reactivation.
>
> B
>
>
>
>                       "John W. Colby"
>                       <jwcolby at colbyconsulting.        To:
>    "AccessD"
> <AccessD at databaseadvisors.com>
>                       com>                             cc:
>                       Sent by:
> Subject:  [AccessD]
> forced logout
>                       accessd-bounces at databasea
>                       dvisors.com
>
>
>                       11/02/2004 09:01
>                       Please respond to Access
>                       Developers discussion and
>                       problem solving
>
>
>
>
>
>
> I am almost finished with a class and a table to allow me to
> force a logout
> of my users from  the db.  In fact it is all working now, the only
> remaining
> question is "when do I let them back in".
>
> Is anyone else doing this?  What is your answer?  My tendency is "keep
> logged out between ThisTime and ThatTime", i.e. add a second
> time field to
> the table that is the time to allow back in.
>
> Anyone?
>
> My current system uses:
>
> usysTblShutdown:
>
> SD_ID                    - autonumber PK
> SD_Name            - Shutdown name
> SD_Time            - Time to shutdown
> SD_Enabled         - THIS shutdown is enabled
> SD_Warnings        - The number of warnings to display before
> forcing a
> shutdown
> SD_WarningTime           - the number of seconds between warnings
>
> I have a form that my framework opens that initializes the
> framework, and
> shuts it back down if the form tries to close.  Thus enabling a clean
> shutdown regardless of anything other than perhaps a power failure.
>
> I then use the timer for this form to call a method in my class which
> checks
> whether to do the shutdown.  The class raises an event with
> every warning
> to
> the user in case your app needs warning that a shutdown is
> imminent.  The
> class also raises an event when it is finally time to actually do the
> shutdown.
>
> I will publish the whole in a demo database as soon as I
> handle the issue
> of
> when to allow them back in.  All opinions welcomed then summarily
> dismissed.
>
> ;-)
>
> John W. Colby
> www.ColbyConsulting.com
>
>
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
>
>
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
>
>
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>