Hi, Kevin!

>>
First of all, Paul is correct that MM VFP COM objects automatically run in private data sessions. Secondly, the business objects are simply getting information from goApp rather than storing a reference to themselves. Once goApp is created, business objects can use goApp to reference manager objects such as the Factory and the Database Manager.
<<

This is absolutly true - and it's also absolutly clear to me (now :-))!

But my problem comes due to using an application object derived from cApp.vcx::cApplicationCom in the ASP.NET apartment threading model to have the advantages of an existing goApp (I don't instanciate BOs as COM objects, I instanciate an application object as an wrapper which creates the needed BOs):

- first hit creates a MMF COM application object in the first apartment, which saves it's reference into goApp
- second hit from another user (some milliseconds later) creates another instance of the same MMF COM application object in the second apartment, which saves it's reference into goApp too
- that means, the first reference is overwritten, and some code in the first instance may use the second instances goApp!

Is my error the usage of a cApp.vcx::cApplicationCom derived class in ASP.NET environment - or where I'm wrong?

In other words: What is the common way to deal with MMF BOs in ASP.NET environment?

TIA!