Must I call CreateObject on ADODB components to get proper protection? 1

[entaroadun]

I have a component registered in COM+ that doesn't support transactions. It performs database-read operations with ADO.

Can I call:
Set cn = New ADODB.Connection

or do I have to:

Set cn = CreateObject("ADODB.Connection&quot

The connection is to a SQL Server 7. I know SQL Server will enforce connection pooling and all that but do I need COM+ to get involved as well for the resource savings?

If the question doesn't make sense, please let me know. I am new to this and my understanding of COM+ may not be conceptually correct.

 

[SemperFiDownUnda]

Depends on if you are using MTS or Component Services.
In both cases if you don't care about the connection being in the current transaction then
Set cn = New ADODB.Connection
is fine.
Under Component Services that works the same as GetObjectContext.CreateInstance("ADODB.Connection&quot
Under MTS if you want a component to participate in the current transaction then you must use CreateInstance.

Hope this answers your question.