>I don't have your huge experience with web apps. Can you explain why it isn't scalable and what other
>problems may arise, please?

Anything that is loaded as an Application object var is essentially the same as a global var, which means it's shared by all users and pages in a Web site. If you have an object and two pages want to access that object it gets queued. If the object is not free threaded IIS will block all access to any other COM object until the call completes. If it is free threaded it will make the call and add implicit Application.lock/Unlock's around the object access.

>>That code above is no good anyway - if you load any application specific objects they should be OBJECT tags in global.asa, never loaded like that.

Object tags in Global.asa can be running simultaneously if they are free threaded, but only if they are free threaded. Again I don't know whether WSH is free threaded (or marked as Both which assumes it supports freethreading).


Basically you should avoid Application object use just like you avoid using globals in a VFP application. Use only when absolutely no other way is available to share data.