Yes, in my case, I wanted to be able to pull up information about a process that was doing an http upload on another ASP/VFP MTDLL thread. This was for a graphical representation of the progress of the upload in a small browser window. I too had heard that public variables could be seen by another ASP session but didn't realize it was confined to that same thread. I thought an array would be ideal to hold this info, but, ended up using a temp table instead which actually works just as well in this case..
>Do you mean you built an MTDLL for use with IIS/ASP? I'm still not sure just what is happening with ASP. I'm basically looking for a fast way to share small amounts of data that needs to remain global and persistent among all instances of an object. The equivalent of sharing memory among several processes.
>
>I concerned about what happens with the overhead factor when you use a COM EXE as a "global content holder" for objects instanced from one or more MTDLL's (this is what Nick was suggesting, no? ). Isn't there a way to achieve the same end with the MTDLL itself?