[thelist] Protect update in webapplication

[Rob Smith]

>IS there some way to kick out all users (preferably terminating their
>work in a nice orderly manner)?

I would stay away from using Access altogether if you're updating the
database frequently enough. Your users will start to lose faith in the
system if they're constantly being kicked off. Using a more advanced
database solution will stem kicking people off. 

>Is the best way to just loop through all the session variables and flag 
>them accordingly?

If you must, you must. You can also just send an email to all the users of
the system that it'll be down for "system maintenance" from X:XX to Y:YY and
that everyone should get off the system during that time. Once the lock file
disappears, make your changes. And/or make your upgrades on the weekend when
no one uses it.

Alternatively, if you're in an international company, Friday at 5pm + is the
best time. Europe is asleep and Australia/Asia is on Saturday
morning/afternoon. 

Speaking from the trenches,

Rob