Posted by
eric ehlers on
URL: http://quantlib.414.s1.nabble.com/RE-Err-Msg-Not-excel-add-in-format-for-Object-Handler-examples-tp4526p4530.html
Hi All,
To clarify:
- ObjectHandler and QuantLibAddin are supported subprojects of
QuantLib, implemented using the Excel C API (XLLs)
- Liu and Jerry are troubleshooting a QuantLibAddin error message
- Amitesh is talking about scrapping ObjectHandler and QuantLibAddin
altogether and implementing something new in a different technology
e.g. automation
Let me address these issues separately:
1) "Addin not in Excel format" error message from QuantLibAddin
On 2/28/06, Liu, Xiaobo <
[hidden email]> wrote:
> > Hi,
> >
> > I complied both latest versions of ObjectHandler
> > and QuantlibAddin, but could not load up
> > any *.xll files due to error msg stating that
> > the xll files are NOT of Excel add-in format.
On 3/1/06, Jerry Jie Ji <
[hidden email]> wrote:
> Similar problem here, just that I'm using MS VC++ 2005 Express (8)
> and MS Excel (Office) 2003.
On 3/1/06, Sinha, Amitesh <
[hidden email]> wrote:
> 1.
http://www.planatechsolutions.com/xlpfaq/Q0011.htm> essentially open your xll in visual studio tool "depends" and
> see if any dll xll depends on is missing. I suspect log4cxx , oh dll
> may not be in the path. If you do not have depends, go to
> www.dependencywalker.com.
> 2. I am hoping that you are not mixing managed C++ and unmanaged C++ as
> string in managed C++ are treating differently. Most likely you are
> not doing this.
> 3. If point 1 does not rescue you, you may be mixing debug/release
> libraries, just check that you are not doing this.
>
> 4. Using DumpBin /Exports should list the DLLs bound statically to your
> code. You need to ensure they are in your
> path, and not just lying around the target machine.
Please see also:
http://quantlib.org/quantlibaddin/troubleshooting.html#startup_error2) Using automation instead of the C API
On 3/1/06, Sinha, Amitesh <
[hidden email]> wrote:
> XLL technology is getting
> deprecated. Most of your efforts are likely to be lost in coming years.
For a long time it seemed evident that MS were trying to steer
developers away from the API toward newer replacements - VBA/COM/.NET.
Many people continue to use the API because for certain tasks it is
orders of magnitude faster than the newer alternatives. And now it
seems that MS have given up on their attempts to deprecate the API,
apparently Excel 2007 will include enhancements to the API:
http://blogs.msdn.com/excel/archive/2006/01/03/508985.aspxRegards,
Eric