References thru VBA

[past perfect]

Hi,
I have a frontend/backend database. Sometimes when I install the
program on a new machine I find out that there are reference problems.
Is there a way to trap this error in code?
Then perhaps I could delete the reference if I feel I can live without
it.
As an example I reference MSWord. But I have Word 2003. The new user
might have MSWord 2000. I will get an error. If I could handle the
error in code it would look much more professional.
Thanks for your time

 

[Paul Overway]

If the reference is something like Word, Excel, or Outlook...you're better
off not to have it at all. Use late binding instead (see help for
CreateObject/GetObject). Using late binding, you don't need the reference
and can trap error 429 if CreateObject fails.

 

[Douglas J. Steele]

In addition to Paul's suggestion (which I agree with wholeheartedly), you
might want to read what MichKa has at
http://www.trigeminal.com/usenet/usenet026.asp