You amy want to get Rick Article on using VFP COM objects from ASP at www.west-wind.com ...

To answer your question, I think every connection to the multi-threaded COM object will gets its own 'apartment' of properties, methods, etc... I also think you have to host the COM object in MTS to get multi-threading... If you are not using mts I think you need to use Single-USE .exe automation servers... each connnection gets a new instance of vfp, etc.


BOb


>Hi
>
>I have a question on the use of VFP com components from asp pages. The question is regarding multi-threaded com servers that have page level scope - where the object is created and destroyed on the same asp page. (I am not trying to maintain state between requests). With components of this type, is it acceptable to do the following from an asp page:
> - instantiate the com server
> - set some object properties
> - call a method
> - check the value of one or more object properties set by the method
>I don't understand how vfp will handle multiple users accessing the page/component and attempting to access the same pem's simultaneously. Are multiple users each working with their own independent instance of the com server, or will one user's property settings change the values for another user?
>If an asp page calls a component method, is it possible for the method to call other class methods before returning a value to the asp page, or does all logic have to be contained within a single method call?
>
>Thanks and regards
>Bill Sabo