>Robert, I think that Mark was asking how to take advantage of FoxISAPI's pool manager from ASP. Instanciating an object directly from the page won't help here. Mark- if you are still in the beginning phases of this project, I highly recommend having a look at Web Connection. Rick has built his own pool managaer that is more efficient than both MTS and FoxISAPI.

Erik is right on. Here's the quandry I'm in. I know Rick has a pool manager but my understanding is that he also his own session management and session-level variable management that is independent of ASP and ASP's session objects. What I want is to leverage the pool manager (probably solely) to take advantage of the VFP engine and related data-centric business logic that would be embedded in my out-of-process server(s). But I would like to use ASP/Web classes to coordinate the session management. I want to be able to pass the Session, Request, and Response objects from ASP to the methods in my out-of-process server(s) which will be sitting there, already instantiated, with databases open and ready to fly. Or stated a bit differently, I want the same functionality that one can derive from an in-process VFP MT DLL that is easily joined with an ASP/WebClass app... but as an alternative, I want this functionality in conjunction with using pooled, out-of-process servers rather than repeatedly re-instantiating objects within MT DLL in-process servers. Rick has proven (to me, anyway) that this technique provides more bang for the buck.