[AccessD] ACC97 Repair and Compact

Tony, I started creating a system that was a pretty simple and straight
forward method of shutting down end users.  What it used was named pipes.
Named pipes are a pretty easy method of communicating between machines.
Access handles the client code without a hitch.  However, the 'server' code
pauses the thread, which 'locks' Access.  

Essentially what would happen, is you have a VB program (ideally running as
an NT service).  That program sits and acts as a pipe 'server', and listens
to a named pipe.  The FE in Access has a hidden form that fires a timer
event, which used the client code to 'ask' the server what to do.  A simple
'Nothing' reply and it goes on it's way.  The communication is fast and
quick, and is very painless.  You then set a time line on the VB program,
where between a certain period, it starts sending out a 'Shutdown' command,
at which point the clients get 'Shutdown', instead of 'Nothing', and they
start shutting themselves down.

Because the Access FE's would be 'checking in', your VB program would have a
list of FE's that are online, so it would know when they all 'signed off',
and then you could run the compact.

Just a thought....

Drew

-----Original Message-----
From: Tony Septav [mailto:iggy at nanaimo.ark.com]
Sent: Saturday, November 01, 2003 1:08 PM
To: AccessD at databaseadvisors.com
Subject: [AccessD] ACC97 Repair and Compact


Hey John
Mentioned to Dan, that one way around the problem, may be his automatic
shutdown suggestion (during the lag time).
Then Task Scheduler to run the repair and compact, then after a certain
time period have the Task Scheduler open the program again. Not as
pretty as automating but an alternative if need be.

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