Invocation stack

[ElvisSteel]

Hi,

Not sure if terminology correct, but this is what I need advice on...

I have a workbook that gives the user a start screen (via coding in Workbook_Open) and then carries out a number of steps.

At various stanges they can abort the process and I want to ensure that when this happens they are returned to the start screen.

I can just call the start macro when they abort, but in doing so do I cause a potential memory problem in that I am invoking a call from within a call from within a call etc and this could happen repeatedly.

So a number of questions...

1. Am I worrying unnecessarily?
2. Is there a better way of imposing this type of process?

Thanks

Steve

 

[Ruddles]

I think you're worried about doing this:-

sub workbook_open()
  call start_screen
end sub
 
sub start_screen()
  [COLOR=green][B]' carry out some stuff[/B][/COLOR]
  if abort_by_user_detected then call workbook_open
end sub

Every time you come out of 'carry out some stuff' with a detected abort condition, you call workbook_open which in turn calls start_screen which might again call workbook_open... each time placing the return address on the stack.

You're right - this will end in tears! Try to contain the looping mechanism within a single procedure, like this:-

sub workbook_open()
  call start_screen
end sub
 
sub start_screen()
  do
    [B][COLOR=#008000]' carry out some stuff[/COLOR][/B]
  loop until abort_by_user_detected 
end sub

Did I understand the question correctly?