J:

My intention is to have two layers. The ASP-dependent layer would decode parameters and form values and pass them to the ASP-independent layer. This would allow both ASP and non-ASP processing.

What I have already done is set up a single ASP page that instantiates, calls, and releases the stateless ASP-dependent object running under MTS. This object is supposed to decode the QueryString and form values, determine which object to call, and call the appropriate ASP-independent object. It's all data-driven and properly OOPy, except for one thing: I can't figure out this gol' darn syntax to pull out the form values and QueryString values!

It's frustrating to be hung on such a simple point, because the articles that yourself and other helpful souls pointed me to really caused all of the casual reading I've been doing to fall very neatly into place, and now I am really itching to get moving.

>>J:
>>
>>>
>>>Sorry, I might have misunderstood the question. Is this call from within a COM object or from the ASP Script?
>>
>>This is a call from within the COM object, trying to reach back to the ASP intrinsic object to get things like submitted form values and parameters.
>>
>>So that if I call /Localhost/MTSTest.asp?SomeParm=Hello, I would like to "see" the parameter from within the COM object.
>>
>>The docs on MSDN are quite thorough, but they are all in VB, and I am having trouble translating the syntax into something that will work.
>
>Have you considered passing the values as parameters instead?
>
>The way you are coding it the component would be tied to running under IIS, and would be tightly coupled with the specific ASP script / HTML page that calls it. On the other hand, if you pass parameters the component could be used by other clients if the need arises.