Access 2007 Runtime: Missing Excell Object Library

[Rocky]

I have included a utility in my development that references to MS
Excel 12.0 Object Library.

How do I package the Object Library to be included in the runtime
version that will run on machines that have Excell 2002 on it.

Dio I have to reference MS Excel 10.0 Object Library and if so, where
do I find it and how does one add it to the package?

Rocky

 

[RoyVidar]

I have included a utility in my development that references to MS
Excel 12.0 Object Library.

How do I package the Object Library to be included in the runtime
version that will run on machines that have Excell 2002 on it.

Dio I have to reference MS Excel 10.0 Object Library and if so, where
do I find it and how does one add it to the package?

Rocky

I would switch to late binding.

Tony Toews has a page with some info and links
http://www.granite.ab.ca/access/latebinding.htm

Remeber that when using this, you would remove the reference to
the automated application, which means that the constants from
that application wont work, either.

Some resolve that by defining their own constants

Const xlPasteValues as long = -4163

Some will just replace it with literal

mySheet.Range("A1").PasteSpecial -4163 ' xlPasteValues

 

[Guest]

IN addition, it is important to note that the target computer must have some
version of Excel installed.
It is not legal to include Office objects in your package that are not part
of Access.

 

[Tony Toews [MVP]]

IN addition, it is important to note that the target computer must have some
version of Excel installed.

Assuming you want to use Excel at all of course. The reason for using
late binding is either for different versions of the reference or if
the reference, such as Excel isn't even installed. Sure it'll error
out if someone hits that code but at least the rest of the app will
execute.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Rocky]

Assuming you want to use Excel at all of course. The reason for using
late binding is either for different versions of the reference or if
the reference, such as Excel isn't even installed. Sure it'll error
out if someone hits that code but at least the rest of the app will
execute.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems athttp://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/

Thank you Tony, Dave and Roy

I had to do quite a number of changes to my code,
but in the end it worked on my machine without any reference to the
missing Objct Library.

I now need to test it on the other machines, but I am sure it will
work. Please be rest assured
that all the target machines have licenced copies of Excel

I read the comments about speed being slower with late binding, we
will have to wait and see.

It is so good to know that one has the world behind you, especially
when one ids fairly new at VB code

Thanks

Rocky