Thanks Craig

>>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
>
>You can do it that way. However, it is better to pass everything via parameters and then get the return value. Don't set properties.
>
>>I don't understand how vfp will handle multiple users accessing the page/component and attempting to access the same pem's simultaneously.
>
>As long as you keep the component instantiated you're ok.
>
>>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?
>
>Yup. Just avoid PUBLIC variable, but you should do that anyway.
>
>>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?
>
>You can call as many components/methods as you want.
>
>>
>>Thanks and regards
>>Bill Sabo