Maybe you could develop your code with the references, 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

anthony wrote:

Hi

I am distributing a vb project that opens up and runs excel macros. When I
distribute the package it install fine but as soon as a spreadsheet is
opened I am getting errors and I have found that there are missing reference
in the sheets.

When I package the VB project I add the sheets to it but it does not find
the references that the sheets need.

Does anyone have an idea how I can package a VB project with Excel
spreadsheets that contain references and have the VB project detect the
references and add it.

Thank you
ant

--

Dave Peterson