>
>That means for the MMF COM object:
>- first hit creates a MMF COM object in the first apartment, which saves it's reference into goApp
>- second hit (some milliseconds later) creates another instance of the same MMF COM 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!

When does the bizobj register itself with goApp?

>BTW: A similar problem comes from the usage of the default datasession in MMF COM abjects, which also overrides or crashes in some circumstances - using a private datasession instead seems better to me - what is the recommended way???
>

When running in COM mode, it should automatically create it's own datasession. Take a look at the code in COMInit(). The one question I've got about it is that the tlComUseDefaultDataSession parameter is passed via the Init() in KBizObj. If it's a COM component, you can't ever pass it a .T. (since you can't pass parameters to the Init() of a COM control). The only way around this would be to create another proxy object that creates your business objects for you.