That is true if you are developing for a distributed app or in situation
where you have different versions of the "Reference".
See:
http://support.microsoft.com/default.aspx/kb/245115
Although from a Word MVP here is an easy to read list
http://word.mvps.org/fAQs/InterDev/E...ateBinding.htm
Even
http://www.granite.ab.ca/access/latebinding.htm
who proposses Late binding suggests:
"You'll want to install the reference if you are programming or debugging
and to use the handy object IntelliSense code expansion while in the VBA
Editor. Then once the code is running smoothly change the conditional
compiler constant. "
So at least start with the "Early Binding" and decide later or use the
coding technique from the above Latebinding.htm
"Pendragon" wrote:
> Actually, ryan, the way you are defining and calling the Excel objects --
> late binding -- is the preferred method by the gurus of Access from what I
> have read in these forums.
>