I keep getting an error 16 "Expression Too complex" message when I run a subroutine. The problem goes away when I break in the code window and resume but I want to figure out the source off the problem. The line that causes the error is:

dblOrderData(iTab, ORDER_IX.Buy_Price, iInstrument) = 0

dblOrderData is a 3 dimensional array of doubles. The Microsoft help says that this error occurs when more than 8 nested floating-point calculcations take place at the same time but here I am simply setting the value to zero.

Does anyone ave any ideaa?

Thanks

John

John,

Whats the "ORDER_IX.Buy_Price" value and where does it come from?

Regards,
Rob

"ORDER_IX.Buy_Price" is an enum value and equal to 0

Whats the state of the variables at the time, how are they initialised?

I have never experience this one before myself, and Im struggling for ideas, may be useful to understand a bit more about "behind the scenes".

Regards,
Rob

The state of the variables before the line:

dblOrderData(iTab, ORDER_IX.Buy_Price, iInstrument) = 0

iTab=0
ORDER_IX.Buy_Price=0
iInstrument=0

ubound(dblOrderData,1)=0
ubound(dblOrderData,2)=6
ubound(dblOrderData,3)=92

I have an error handler in my code as follows:

[...]
GoTo ExitProc

ErrorHandler:
    If Err.Number = 16 Then
        'expression too complex error
        Resume
[...]

And I have set a breakpoint on the Resume line. If I hit F5 (Continue the code after it breaks), it runs OK but I just don't get why it breaks in the first place.

How about the Call Stack?

Sorry to keep digging for info, but you've got my curiosity! =)

Rob

there's only 3 things in the call stack. Tough one huh?

It consistently happens in the same place even if I restart excel. i think i'm just going to have to stick with my resume hack.