OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Kjell Arild Tangen (kjell.tangenCOMPUTAS.COM)
Date: Fri Mar 08 2002 - 01:12:45 CST

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

    You can use ODBC through the OLE DB Provider for ODBC, and that is what was
    done here, since apparently ADO was used. This provider supports automatic
    enlistment in DTC transactions (COM+ transactions) just as the native OLE DB
    provider for SQL Server does.

    Regards,
    Kjell Tangen

    -----Original Message-----
    From: Jonas Blunck TACMa [mailto:jobuTAC.SE]
    Sent: 8. mars 2002 08:05
    To: DCOMDISCUSS.MICROSOFT.COM
    Subject: Re: COM+ Transactions

    I think you must use the OLEDB provider if you are opening and closing the
    connection between method calls. COM+ must be able to manage the connection
    for the transaction stream, and COM+ can only to this with an OLEDB
    provider. I'm not 100% sure about this, but I cannot imagine how COM+ would
    solve this for an ODBC provider. Using an ODBC provider, I think you will
    end up with different transactions for every open/close on the connection
    object you issue.

    Can anybody verify this?

    ----------------------------------------------------------------
    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