Maybe you could develop your code with the reference, but before you release it
to others, you could convert it to use latebinding.

Dick Kusleika has a web page at:
http://www.dicks-clicks.com/excel/olBinding.htm
that explains this with Outlook

Tom Ogilvy posted this recently:

Here are some more extensive references on binding:

Use late binding - don't have a reference to excel.

http://support.microsoft.com/default...b;EN-US;244167
INFO: Writing Automation Clients for Multiple Office Versions

http://support.microsoft.com/default...b;en-us;245115
INFO: Using Early Binding and Late Binding in Automation

http://support.microsoft.com/default...b;en-us;247579
INFO: Use DISPID Binding to Automate Office Applications Whenever Possible

Sheldon wrote:

I am creating an Excel workbook with lots of VBA code. I cam creating this
in Excel 2000 (aka Version 9). At least 90 % of the employees at my site use
Excel 2000. However, whenever my boss opens the workbook, the references get
changed for his use. He uses Excel 2003 (aka Version 11). When I go back in
the reference is broken. I cannot find Microsoft Office 11, naturally.

It seems the references change automatically when the user has a newer
version of Office, but not so when the user has an older version of Office.

I'm not so concerded about my boss breaking my reference, but when the
product is rolled out, I expect this to happen even more. The prodect will
be placed on the interned, the authorized users will download it to their
desktop and run from there.

How can I fix this problem? How can I make the reference upgrade work in
both directions of versions? Maybe I don't really have a problem and don't
realize it?

Thanks

--

Dave Peterson