UDF that works under Excel 2003 but not under Excel 2007

[Joannes Vermorel]

I am working on an addin that define an UDF following an approach
similar to
http://blogs.msdn.com/andreww/archive/2006/07/23/675939.aspx

The UDF gets listed correctly under Excel 2003 (and recognized as well
in the spreadsheet). Yet, under Excel 2007, I get #NAME! warning for
the UDF, and the function does not appear to be listed in the function
list.

Does anyone know what could be the typical incompatibility issues
between Excel 2003 and 2007 regarding registration of UDF?

Thanks in advance,
Joannès
http://www.lokad.com sales forecasting

 

[JLGWhiz]

This site might help.

http://msdn2.microsoft.com/en-us/library/bb226683.aspx

 

[Tony Gravagno]

Also, there is a new Com Shim Wizard v2.3, and Andrew posted a bug
report and patch for code generated by that release. See my blog for
info. If anyone can tell me where my deployment is going wrong I'd be
grateful. Joannes - does the lokad open source documentation provide
deployment details?

(Going to take a closer look at Lokad for other apps)
Good luck with v2007
Tony Gravagno
Nebula Research and Development
remove.pleaseNebula-RnD.com/blog/tech/2007/11/excel-tools5.html

 

[Joannes Vermorel]

Tony, JLGWhiz, thanks for the links and the support. I will have a
look.

does the lokad open source documentation provide deployment details?

There is a MsBuild script named "excel-package.proj" in the /
salesforecasting directory that compile the project and generate the
MSI package (WiX is needed).

Best regards,
Joannès

 

[Jon Peltier]

Is this a dot-net thing? Are you using the correct PIA for 2007?

- Jon
-------
Jon Peltier, Microsoft Excel MVP
Tutorials and Custom Solutions
Peltier Technical Services, Inc. - http://PeltierTech.com
_______


Tony, JLGWhiz, thanks for the links and the support. I will have a
look.

does the lokad open source documentation provide deployment details?

There is a MsBuild script named "excel-package.proj" in the /
salesforecasting directory that compile the project and generate the
MSI package (WiX is needed).

Best regards,
Joannès

 

[Joannes Vermorel]

Is this a dot-net thing? Are you using the correct PIA for 2007?

That's a .NET project with a C++ shim wrapper. Not use what "PIA"
stand for (please apologize my ignorance).

Best regards,
Joannès

 

[Chip Pearson]

Not use what "PIA" stand for

PIA = Primary Interop Assembly. It is a redefinition of a COM object into a
NET assembly. The Excel PIA redefines the existing COM Excel application in
NET compatible terms.


--
Cordially,
Chip Pearson
Microsoft MVP - Excel, 10 Years
Pearson Software Consulting
www.cpearson.com
(email on the web site)

Is this a dot-net thing? Are you using the correct PIA for 2007?

That's a .NET project with a C++ shim wrapper. Not use what "PIA"
stand for (please apologize my ignorance).

Best regards,
Joannès