I have EXCEL2003/SP3 as part of Office Pro 2003 and Windows XP. I have a
workbook with my own user functions in VBA macros, When I save workbook
(with only a single worksheet in it) as web-page and in interactive mode
and open the saved file in my Internet Explorer 7, the user-defined function
in my macro all show up as VALUE# i.e. are not recognisedas Macro functions
as they should be. What is wrong?
I am answering my own question.
Unless an MVP corrects me and tells me otherwise, then user defined
functions do not work even if you save the spreadsheet in interactive form
as a web-page (an *.htm file).
You have to save the spreadsheet as an *.xls file and you can send it to
your webpage but I think a third party downloading the spreadsheet from your
website has to have EXCEL on their PC and then all the user-defined
functions in VBA work fine.
I am not sure about Automation add-ins i.e. functions that are written in
Visual Basic proper (not in VBA) and pre-compiled in VB and then registered
as *.dll in the Registry and then Added- in to EXCEL. Does anyone know?
>I have EXCEL2003/SP3 as part of Office Pro 2003 and Windows XP. I have a
>workbook with my own user functions in VBA macros, When I save workbook
>(with only a single worksheet in it) as web-page and in interactive mode
>and open the saved file in my Internet Explorer 7, the user-defined
>function in my macro all show up as VALUE# i.e. are not recognisedas Macro
>functions as they should be. What is wrong?
David - 12 Jan 2008 08:06 GMT
RE. paragraph below - Automation add-ins i.e. functions that are written in
Visual Basic proper (not in VBA) and pre-compiled in VB and then registered
as *.dll in the Registry and then added- in to EXCEL as Automation Add-ins,
seem to wrk.
.
>I am answering my own question.
>
[quoted text clipped - 19 lines]
>>function in my macro all show up as VALUE# i.e. are not recognisedas Macro
>>functions as they should be. What is wrong?