In my opinion
The primary advantage of late binding in an application which you are
distributing to other users is that you won't get an error if they have a
different reference of the object library than you used to develop the app.
(if you use arguments not available to their version you will still have
problems - but that is a challenge you should meet).

If you can be assured this will not be a problem, then early binding offers
the fastest performance.

here is some additional information:

http://support.microsoft.com/default...b;EN-US;244167
INFO: Writing Automation Clients for Multiple Office Versions

http://support.microsoft.com/default...b;en-us;245115
INFO: Using Early Binding and Late Binding in Automation

http://support.microsoft.com/default...b;en-us;247579
INFO: Use DISPID Binding to Automate Office Applications Whenever Possible

Address some of the issues.

--
Regards,
Tom Ogilvy

"jason" wrote in message
om...
I've been in de Bruin's website and he recommends (for binding Outlook
from inside Excel) using early binding first, because its easier to
write code with, and then to switch your code to late binding, as
it'll stand the test of time better

A friend at work understands late binding but swears by early binding

Any opinions - or can both be advantageous in different situations?

Jason