Are you using the VFP session class? Also, you should ALWAYS compile to a VFP mtdll.
>Hi, folks!
>
>I've a problem using ASP.NET and VFP COM objects which seems unbelievable to me:
>
>- A ASPX page creates an instance of a VFP COM DLL
>- I call the page from the browser – all works fine: In my COM object I check whether a special table "MyTab" is open – it isn't and I open the table in the default datasession.
>- Now I call the same page from another work station: In my COM object I check whether a special table "MyTab" is open – it is currently open!!!!
>
>Further investigations show: both COM objects are running in the same VFP session!
>
>Can anybody this explain to me – I'm totally confused, because I expected to get a second VFP instance for my second COM object instance!
>
>BTW: My COM server is a single threaded DLL, but I've the same problem using a multi threaded DLL!
>
>BTW: Are there any .NET configuration settings to control this behaviour?