What do you mean by "the website is locked"?!?

All that happens is that access to application variables are prevented until
.unlock is called. Which is what you want in the absence of any sort of
collision detection system...

Cheers
Ken

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
From: "B. LaMontagne" <bill@t...>
Subject: [proasp_howto] Application.Lock


Hey all...

I haven't been able to find much information about this, but another
developer
told me that when you use Application.Lock, the entire website is locked
until Application.Unlock is processed.

Obviously this would have some pretty serious implications...  I've done
some quick and dirty testing, and it seems to be true.

So when you need to store Application variables, what is the disadvantage
of *not* doing an Application.Lock?  I don't like the idea of locking up
users unnecessarily just because we need to make some administrative
changes.

I suppose we could conceivably make sure to do no processing during this
period, and that would help, but I'd prefer not to lock them out at all.

Soooo...  Let me know.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~