Comments on: Installing an Excel Add-In

By: Lauren @ Sugar Coated Sisters

Lauren @ Sugar Coated Sisters — Fri, 23 Dec 2011 18:15:52 +0000

This is amazingly useful… thanks!!

By: Jon Peltier

Jon Peltier — Thu, 04 Aug 2011 17:45:26 +0000

Satish -

References are added to a given workbook. If you add them to a workbook today, and open a different workbook tomorrow, then there are no references, because you added them to a different workbook.

If you added references to an add-in, you must explicitly save the add-in. Excel will not warn you if you are closing an add-in without saving changes.

By: Satish P

Satish P — Thu, 04 Aug 2011 16:51:09 +0000

Hey: I have office 2007 and that I run macro based worksheets and wanted to include a series of reference object library. Everytime I check those in the TOOLS>References dialig box and say OK. Next time around when I open the EXCEL workbook, it seems like they are unchecked again. Do you think this could be solved by some means. Thanks

Satish

By: Duncan

Duncan — Fri, 25 Mar 2011 09:52:22 +0000

Yes -and I have now re-compiled using isAddIn property = false and saving it under a new name as xlam.
This has confused the issue even more as I cannot get rid of the references to the xla and xlam which I have previously used and do not want any more.
XL calls up a previous version now.
Alt f11 shows me 2 x xlam – I only want to see one of them.
And the problems with environ and date persist.

How can I clean up these references?
I am using XL 2010 and Win7
Duncan

By: Jon Peltier

Jon Peltier — Thu, 24 Mar 2011 19:58:11 +0000

Duncan – Have you compiled and saved the add-in as an xlam file?

By: Duncan

Duncan — Thu, 24 Mar 2011 15:38:28 +0000

I’m using a Date Box = dtpicker..n to get the date and that is definitely OK. Just tried a msgbox (dtpicker2) and that works ok. That is not the problem.
Thanks for the advice regarding 64-bit!
The problem appears to be with “standard” code like environ and date – the add-in just isn’t finding these.
For example, I use the environ(“username”) to give me the logged-on name.

As I said this morning (CET) these instructions work OK in a 2 line macro but not in the add-in.
It’s something to do with the compilation and/or available libraries etc – but what?
Duncan