[AccessD] Force Closing the FE

I did this once!  The user's were not happy.
Some opened the database and kept it open all day.  Sometimes it would be
idle for hours.
Instead, what I did was to force close the FE's whenever I needed to do
maintenance.

I placed a small text file in the directory where the BE resided.
To force everyone out, I changed the extension from txt to something else.
Code in the frontend would periodically look for the file and if the
extension was changed the user would get a pop-up form indicating the
database would shut down in 1 minute for maintenance. 

I found the code and method here: http://support.microsoft.com/kb/304408 
It worked for me.

Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jennifer Gross
Sent: Monday, February 14, 2011 11:58 AM
To: AccessD List
Subject: [AccessD] Force Closing the FE

Hi Everyone,

 

I have a distributed FE linked to a common BE, with no control over force
closing the FE from a network perspective.  Is there a way to put a timer on
the FE so that if it stands idle for an hour or so, or if a certain time
passes, say 7 PM or midnight, that the FE will Exit?  That way I can be
reasonably assured that all FE are closed and the lock on the BE will be
released for maintenance.

 

I have always had some sort of network control over getting into a user's
workstation once the culprit has been identified and closing down the FE, so
I've never been faced with this issue.  Am wondering how you all handle it.

 

Thanks in advance for your help.

 

Jennifer Gross

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