Eric,
> What value do you get exactly? I get a PV of zero. Do
you get #NA? If so,
> please right click in the cell and select
"Display Error" - what does that
> say?
I get #Value in this cell and #Num in
some others. Take a look at the attached image.
> File qlxl\register\addin.cpp, function xlAutoClose(). But the fact
that the
> earlier crash did not produce a stack trace indicates
that the crash is not
> associated with a specific line of QLXL
source code. It could still relate > to
> memory corruption
triggered by earlier misbehavior of the XLL.
You are right. The debug ended before the Excel
exception.
> An earlier version of QuantLibXL.xla crashed because
of a stack overflow in
> VBA code, in that case also the debugger
never stopped in the XLL.
I make some test and
the error is not in VBA itself.
> Frederik reports a crash using
QuantLibXL-vc80-mt-s-0_9_6.xll only, no
> QuantLibXL.xla, I'm unable
to reproduce his results, are you?
I can
reproduce it. I open
Excel, QuantLibXL-vc90-mt-sgd-0_9_6.xll, RelinkableHandles.xls
or CmsCouponPricers.xls and close Excel in order to crash it. I only crashes
if I open one of these spreadsheets.
In the other
hand, if I coment those files in QuantLibXL.xla it doesn't crash. Nowadays
my QuantLibXL.xla doesn't have these files and it is working without
exception.
At RelinkableHandles.xls the
formula =qlWorkbookPath(Trigger)&"\..\Data\XML\010_StartUp\010_RH\"
returns #Name because of qlWorkbookPath, but it happens in the others startup
spreadsheets too.
Any idea? I think we are almost
there.
Regards,