>>>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.
>>>
>>>Here's the code to get the Thread Id.
>>>
>>>DECLARE INTEGER GetCurrentThreadId IN WIN32API
>>>
>>>RETURN GetCurrentThreadId()
>>>
>>
>>Is the COM server a MTDLL?
>
>Yes. Do you think it is a limitation of PWS?
Quite possibly- but it could also be a timing issue. Is the process you are calling a long one? I think that vfp6t.dll will only create a new thread if it has to- so if you are calling the methods what seems like simultaneously, the server could really be finishing in time to use the same thread for the second call.
But this could all be different on PWS, I don't know.
Erik Moore
Clientelligence