Excel Objects used in Access

[Guest]

I have an Access application that uses Excel Objects within the Access VBA
code. I of course have to add the reference to the Excel Objects Library to
do so. It currently is using the Excel 11.0 Objects Library which is for
Office 2003. How do you package and deploy this application to machines that
do not have Office 2003 and therefore do not have the Excel 11..0 Objects
Library when you don't have the Office 2003 Developer's Edition?

 

[Douglas J. Steele]

I'm not sure that the Developer's Edition allows you to distributed the
Excel object library, so even having it might not help you.

 

[Brendan Reynolds]

Doug is correct, the object libraries for the various Office applications
are not redistributable. You need to use late binding. You'll find plenty of
information on the subject of late binding and early binding in the MSDN
library (http://msdn.microsoft.com/library)

--
Brendan Reynolds (MVP)
http://brenreyn.blogspot.com

The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.

 

[Van T. Dinh]

The target machines will need to have Excel 2003 installed.

If the target machines have only ealier versions of Excel, you may be able
to use late-binding and provided that your code only uses features available
in the earlier versions of Excel, your code should work.

Check Access VB Help on "late-binding".