don101 has brought this to us :
Hello,

Have an Excel 2003 workbook with macro's and a custom add-in which we are
trying
to get to work in a WinXP-SP3/Excel-2007 system. Have fought our way through
digital signing and getting it to open without macro security warnings and
are saving as .XLSM without problems.

BUT... on loading as an .xlsm (or as a compatible mode 2003 .XLS) we
immediately
get the infamous "The following features cannot be saved in macro-free
workbooks: VB project.... etc" message.

Answering either "yes" or "no" gets rid of the message and
then everything seems to work fine.

The workbook accepts a load of data entry then uses the add-in to process
the data, create a new folder and write a non-excel format data file.

Any idea why we are seeing this on the load (would expect it on save) and
how do
we stop the message?

Thanks

DonJ

What confuses me is why does an addin's workbook have its own macros if
that workbook belongs to the addin? I'd expect all macros to be inside
the addin so its working files are macro free. At least, that's my
understanding of why addins are addins and working files used by addins
are just normal workbooks without macros.

As for the notification you're seeing on startup.., is there code that
does a save process whenever the file is opened? (Perhaps recording a
last opened date or ?)

Why does your addin allow XLS files to be saved as later version files
if your project needs to run on early versions too?

--
Garry

Free usenet access at http://www.eternal-september.org
ClassicVB Users Regroup! comp.lang.basic.visual.misc