Yes, you can create the transaction explicitly whenever you need one. But,
COM+ doesn't create the transaction inside the database until you actually
access the database. Then you can explicitly tell COM+ to commit/rollback
the transaction whenever you want to. You have a pretty good control of the
transaction when running inside COM+.

The main reason for you to create your own transactions would probably be to
avoid the DTC, i.e performance overhead if you only access one resource
manager in the transaction.

Cheers,
  Jonas

-----Original Message-----
From: Shai Segev [mailto:shai_segev_HOTMAIL.COM]
Sent: den 15 januari 2003 15:30
To: DCOMDISCUSS.MICROSOFT.COM
Subject: COM+: Creating a transaction programatically

According to MSDN you can set a COM object under COM+ to require a
transaction. This cause a transaction to be created when the object is
called. The question is, can one write an object that support transactions,
but create the transaction explictly when needed?

Thanks,
Shai Segev

_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

----------------------------------------------------------------
Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
contains important info. Save time, search the archives at
http://discuss.microsoft.com/archives/index.html . To unsubscribe,
mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM

----------------------------------------------------------------
Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
contains important info. Save time, search the archives at
http://discuss.microsoft.com/archives/index.html .
To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]