Automatic Transactions Not Automatic?

[Terrance A. Crow]

I may be missing something very basic here, but I've written a a group
of three DLLs in VB6 Enterprise Edition. One is the root, and it's set
to require a new transaction. The other two are set to require a
transaction. The first simply calls the other two and checks a
property; if either one fails, the root calls SetAbort.

I've installed these objects via the Component Services console on a
Windows 2000 Server. I have an IIS application that calls the root
object. If the second object fails, the first database update does not
get rolled back.

Is that the correct behavior? Or am I missing something?

And is it also true that COM+ can't pool VB6-created objects?

Thanks in advance!

[Colin Saxton]

Try using createinstance to create the child MTS objects. Wehn an MTS object
creates another MTS object then you use to have to use createinstance to
make sure the objects were in the sam context. MS say that you do not have
to do this with com+ but with com you do. If you are using com+ then its
still worth a try. Sorry I can't help any more than this (for now).

Terrance A. Crow <oh...@youdont.com> wrote in message
news:38ee02f8...@netnews.worldnet.att.net...