Hi Nelson

... Excel is smart enough to switch to the Microsoft
Office 10.0 Object Library.

.... and after all this she's stupid enough to actually save the upgrade for all later
users, yes that goes for ADO and other references too. Bob's right as far as I know, you
can't handle this without removing the references and create late binding by code. This
posting just to add another resource, Dick Kusleika's page
http://www.dicks-clicks.com/excel/olAutomating.htm

--
HTH. Best wishes Harald
Followup to newsgroup only please.

"Nelson" wrote in message
...
I have Excel files that are used by people with different
version of MS Office. These files create an Outlook object
and send emails.

The issue is, when a person with Outlook 2002 uses the
file, Excel is smart enough to switch to the Microsoft
Office 10.0 Object Library. However, next next person with
Outlook 2000 receives compile errors when the Excel code
runs. When I look at the references, it shows, MISSING
Microsoft Office 10.0 Object Library. I have to uncheck
that and recheck Microsoft Office 9.0 Object Library.

Is there anyway to handle this with code?

TIA
Nelson