How do I use late binding to avoid references libraries?

[Glory]

My code has a compile error on computers that don't have an "ADOX 2.8" reference. I have an error handler but it doesn't trigger when a compile error occurs.

I want to exit the sub without entering the VBE when the error occurs. I read that using "late binding" I could avoid referencing libraries in the first place.

http://webcache.googleusercontent.c...d=2&hl=en&ct=clnk&gl=us&source=www.google.com

 

[Glory]

The compile error occurs because of a Dim statement:

"Dim A As Connection"

Is there a way to avoid this without manually setting the reference on every PC?

 

[Glory]

Removing the specific references to "Connection" and "Recordset" (replacing them with generic objects) avoids the compile error.

This only leaves me with one question, which is why the exact same code produces no compile error when it's executed from a separate workbook.

 

[Sektor]

Try to set reference to version 2.5.

 

[Glory]

I'm trying to avoid manually setting references because there are a lot of machines here and they're not all setup at the same time, so it would be a major hassle (unless it could be done programmatically)? Even then the compile error would probably happen anyway before the programmatic solution could trigger, as soon as the workbook opened.

But supposedly there's a way to solve the problem using 'late binding'. I have no clue what that is.

 

[Sektor]

It's this:

Dim cn As Object, rs As object
Set cn = CreateObject("ADODB.Connection")
Set rs = CreateObject("ADODB.Recordset")

 

[Norie]

What code?

Kind of hard to give specific help with it without seeing it.

 

[Glory]

Are you saying late binding is using generic "Object" data types for all objects?

 

[Jaafar Tribak]

I'm trying to avoid manually setting references because there are a lot of machines here and they're not all setup at the same time, so it would be a major hassle (unless it could be done programmatically)? Even then the compile error would probably happen anyway before the programmatic solution could trigger, as soon as the workbook opened.

But supposedly there's a way to solve the problem using 'late binding'. I have no clue what that is.

Late binding is done by using the CreateObject or GetObject Methods to get a reference to a COM object as opposed to setting a reference to the COM Class and using the New Keyword . Late binding is slower and you loose the Intelsense functionality but it is more flexible... and of course, you need to declare all the variables as generic Object

 

[Glory]

Jafar, would you please give me an example of each?


Norie: Posted the wrong thing, I will have to post it in a little while.