CreateObject VS New

[Gensor]

What's the difference between :

Set connTest = New ADODB.Connection

and

Set connTest = CreateObject("ADODB.Connection")

[Jacob Roman]

CreateObject relys on the Registry, while New uses the object itself. Heard the New keyword is better for speed.

[Gensor]

Thanks you!

[brucevde]

Actually, in this case there is no difference. Using New is only beneficial over CreateObject when creating an instance of a class that is within the project.

This KB article explains it pretty well

How Object Creation Works in Visual Basic Components

[RobDog888]

Also, if you use the New style then its best to do it like so.

Dim connTest = ADODB.Connection
Set conTest = New ADODB.Connection
 
'Vs:
Dim connTest = New ADODB.Connection

[chemicalNova]

I assume you meant:

Dim connTest As ADODB.Connection '****
Set conTest = New ADODB.Connection
 
'Vs:
Dim connTest = New ADODB.Connection

..for VB6

chem

[RobDog888]

Umm, for the "New" style, not meaning .NET but the New keyword.

[techgnome]

RD - He was pointing out this "error" in your code:

Dim connTest = ADODB.Connection

At any rate.... there are more significant differences between using "New" vs "CreateObject" and that's the issue of early vs. late binding. If you dim an object of a specific type, then use hte New keyword to create a new instance, you get early binding which is good for ensuring that the object types are correct and you get intellisense to boot. When using CreateObject, typicaly it's with a var dimed as Object, which results in late-binding, there's no guarantee that the resulting object is in fact the right type you are expecting. And since the IDE won't specificaly know the object type, no intellisense is available.

It's possible to combine the two:

Dim rsMine as Adodb.Recordset
Set rsMine = CreateObject("Adodb.Recordset")

but since you'd have to set a reference to get the Dim to work anyways, might as well use the New keyword.

Tg

[dee-u]

Dim connTest = New ADODB.Connection

Isnt it suppose to be like this?

Dim connTest [B]As[/B] New ADODB.Connection

And yap, CreateObject is used for Late Binding hence it might be slower (but you might not notice), it's commonly used in Server Side Scripts...

Dim WdObj as object
...
Set WdObj =CreateObject("Word.Application")

With the above code you gain the ability to work with different version of word.

[RobDog888]

Guilty as charged. That happens every now and then. Its from writting code in .NET and then going back to old VB6. New
habbits are hard to break.

[Pradeep1210]

The basic difference between New and CreateObject:

Objects declared by New keyword are early bound.
Objects declared by CreateObject are late bound.

Just as Jacob Roman said New is faster than CreateObject for this reason.

Pradeep

[brucevde]

Using New or CreateObject has nothing to do with an object being Early or Late bound.

Early or Late binding is determined by the variable Declaration only

Dim X as Library.Class = Early Bound object
Dim X as Object = Late Bound object

CreateObject can be used to create a Late or Early bound object instance.
New can only be used to create an Early bound object instance.

New is only faster if the class is within the project.