--- Alan Williams <[EMAIL PROTECTED]> wrote: > But could you tell me why I should DisableCommit for JIT activated > objects.
I should really have said for transactional components. (Since you are using transactions you are also using JIT activation implicitly). You'll never want to commit a transaction after just an Init call, presumably you'll also have some other work to do, so to mark this it would be best to call IObjectControl::DisableCommit. If you don't then the component is saying 'I'm happy to commit this transaction' (by default - EnableCommit) when it returns from Init. You definitely don't want to call SetComplete or SetAbort in Init which would allow COM+ to deactivate your component and lose its state between method calls. These should only be called after your real work is complete for the object. Peter __________________________________________________ Do You Yahoo!? Yahoo! Tax Center - online filing with TurboTax http://taxes.yahoo.com/ You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
