View Single Post
  #6   Report Post  
Posted to microsoft.public.excel.programming
Tom Ogilvy Tom Ogilvy is offline
external usenet poster
 
Posts: 6,953
Default permanent/programmatic changes to VBA Project References

I guess if there would be problems regardless of whether you used late or
early binding, then yes, I guess it wasn't just unclear, but misleading.

--
Regards,
Tom Ogilvy


"CBrine" wrote:

That's exactly what I was referring to. Sorry if the explanation wasn't
clear enough.

"Tom Ogilvy" wrote:

Why do you think latebinding would have problems with older versions. That
is half the reason to use latebinding. What would cause problems is if you
use features not supported in the older version - but that has nothing to do
with latebinding.

--
Regards,
Tom Ogilvy


"CBrine" wrote:

Forgot to explain why:-)
When using late binding you don't need to use the reference at all. VB will
automatically pick up the most recent associated object based on the
createObject().

"CBrine" wrote:

Have you thought about using late binding instead of early binding? It's
very easy to implement, but could cause problems if the user has an older
version.

Just change all your DIM references for the word object to Object.

ex.
Dim Doc as word.document
To
Dim do as object

HTH
Cal

" wrote:

Hey--Is there any way to permanently select certain references from the
VB Project library? I want to be able to always reference microsoft
word at all times in VB, rather than have my users tell the VB editor
that they would like to reference word...

Thanks,
Abe