Trapping Broken Reference

[NZ VBA Developer]

Is there any way to trap the error for a broken/missing reference in a project?

 

[Shauna Kelly]

Hi

Yes, you can do that, but only if the user has trusted access to the VBA
project - and no sensible IT admin would allow that.

So the short answer is no.

The solution is to use late binding, and check whether your object has been
properly established. I generally sequester code that requires this into
small functions, and make the change to late binding near the end of the
coding process so I can have the advantages of early binding while I'm
working.

There's more info on this at
Early vs. Late Binding
http://www.word.mvps.org/FAQs/InterDev/EarlyvsLateBinding.htm

but it's only available for Wallabies supporters<g>.

Hope this helps.

Shauna Kelly. Microsoft MVP.
http://www.shaunakelly.com/word

 

[NZ VBA Developer]

Hmm... Very interesting but probably won't help in my case. Looks like I'll
have to rely on 'administrative' controls - a properly designed installation
package for rolling out the project to the users. Just hope the client's IT
manager isn't a Wallabies fan - or worse: an England supporter! <g>

Thanks Shauna

 

[Russ]

The Kiwi Koder,

A Google search found this discussion:
<http://www.utteraccess.com/forums/printthread.php?Cat=&Board=84&main=749878
&type=thread>

If that info works for you or you find something that does, please post a
comment back here for everyone's benefit.