Out of Stack Space

[superjacent]

I'm getting 'Out of Stack Space' error messages. The process involves
two forms. Form A opens Form B in dialog mode and passes through
OpenArgs.

Form B contains a 'Tab' control having two pages. The 'Out of Stack
Space' error always (nearly always) occurs when clicking the 2nd page
tab. It doesn't occur anyway else in the project.

On testing, turning off all the 'On Error GoTo' statements the
offending line is set at Form A on the 'DoCmd.OpenForm' statement.
Checking the 'Call Stack' only shows two event procedures, the event
procedure 'command_button _click()' and a 'listbox_DblClick()' event
procedures. As far as I can tell there is nothing recursive
happening.

Any clues please.

[Lyle Fairfield]

superjacent wrote:

I'm getting 'Out of Stack Space' error messages.

Any clues please.

I don't know; Did it pop up right after the 42 DDD message?

[Gord]

I'm getting 'Out of Stack Space' error messages.

Perhaps this applies:

http://support.microsoft.com/kb/96988/en-us

superjacent wrote:

I'm getting 'Out of Stack Space' error messages. The process involves
two forms. Form A opens Form B in dialog mode and passes through
OpenArgs.

Form B contains a 'Tab' control having two pages. The 'Out of Stack
Space' error always (nearly always) occurs when clicking the 2nd page
tab. It doesn't occur anyway else in the project.

On testing, turning off all the 'On Error GoTo' statements the
offending line is set at Form A on the 'DoCmd.OpenForm' statement.
Checking the 'Call Stack' only shows two event procedures, the event
procedure 'command_button _click()' and a 'listbox_DblClick()' event
procedures. As far as I can tell there is nothing recursive
happening.

Any clues please.

[superjacent]

Lyle Fairfield wrote:

I don't know; Did it pop up right after the 42 DDD message?

What's this?

[John Welch]

I'm not sure about your out of stack space error - do let us know what you
find out.
But I wanted to let you know, in case you don't, that you can change a
setting in the vba environment to make the code break on all errors, so you
don't have to go turning off each 'on error goto' statement. It's in
tools-options, not sure which tab now, but you'll find it.
-john

"superjacent" <su*********@gmail.comwrote in message
news:11*********************@e3g2000cwe.googlegrou ps.com...

I'm getting 'Out of Stack Space' error messages. The process involves
two forms. Form A opens Form B in dialog mode and passes through
OpenArgs.

Form B contains a 'Tab' control having two pages. The 'Out of Stack
Space' error always (nearly always) occurs when clicking the 2nd page
tab. It doesn't occur anyway else in the project.

On testing, turning off all the 'On Error GoTo' statements the
offending line is set at Form A on the 'DoCmd.OpenForm' statement.
Checking the 'Call Stack' only shows two event procedures, the event
procedure 'command_button _click()' and a 'listbox_DblClick()' event
procedures. As far as I can tell there is nothing recursive
happening.

Any clues please.

[superjacent]

I think I've sort of resolved this problem. After making many design
changes, one in particular replacing multi-dimensional arrays with
tempoary tables (which in itself didn't fix the problem).

Form A (unbound) calls Form B, modally. Form B (unbound) contained a
tab control with two pages. There are a number of combo boxes on both
pages. On the second page I had a combo box with the rowsource set to
a value list "0,No,-1,Yes". Other settings for this combo were
correctly set. This particular combo box received the focus when
clicking the second page tab. Upon clicking the second page tab is
where I was getting the 'out of stack space' error.

When I changed the combo box to a check box, presto, no more 'out of
stack space' errors.

I realize that this is not a definitive solution but now I can proceed
and hopefully deploy this supposedly simple application sometime during
the week.

Thankyou for everyone's input.

Steve.

John Welch (remove remove) wrote:

I'm not sure about your out of stack space error - do let us know what you
find out.
But I wanted to let you know, in case you don't, that you can change a
setting in the vba environment to make the code break on all errors, so you
don't have to go turning off each 'on error goto' statement. It's in
tools-options, not sure which tab now, but you'll find it.
-john