I'll give that a try. Thanks.

>Those threadIds don't sound valid. This may be an issue with Win95. Try this
>on an NT machine to be sure...
>
>+++ Rick ---
>
>>>>I'm using demo code from West-wind's white papers on Using VFP Com objects with ASP. I am using PWS, instead of IIS, which might be part of the problem. From two differnt work stations calling the same com object, I am getting the sam thread id.
>>>
>>>What are you actually doing?
>>>
>>>IIS/PWS will create COM components on the same thread whenever possible. The only time you'll see different threads is when objects run simultaneously. I'm not even sure if PWS under Win95 supports this but I would guess that it does.
>>
>>This sample is in "Using VFP COM Objects with Active Server Pages" on your website. I'm using the SlowHit function. After reading about the possibility of having two instances of the IE browser possibly using the same thread. I attempted this across a network.
>>
>>Both browsers still we're using the same threads, although one odd thing is that the thread IDs were -58243. Other tests returned high negative thread IDs as well. I may have to test this again across the network simultaneously.