[AccessD] forced logout

>However, I don't see how the app itself can control access - surely once
they have opened it they have activated it in some way.

Well you have to start somewhere, you can't just throw up your hands and not
do anything.  Yes of course once they open the FE things start to happen,
including opening tables etc.  However I can do an IMMEDIATE shutdown if we
are within the time period when the class initializes, not even displaying a
warning.  And if a compact is happening then they can't get in anyway.

I have two specific objectives - getting them out so a compact can occur,
and getting them out so I can edit tables.  Either of these scenarios is
handled beautifully by forcing them out, then doing a brutal shutdown if
they try and get back in.  My class opens an ADO recordset, reads the values
and closes the recordset again, so it's not like a bound form in keeping a
table 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 8:45 PM
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.

In that case I'd go with the manual reactivation approach.  However, I
don't see how the app itself can control access - surely once they have
opened it they have activated it in some way. If the reason for the lockout
is anything then even having them reopen the db could affect the actions
being taken???

B


_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com