F8 and Yellow pattern for compile error
 

Hi,

When I get an error, the offending line in my code would be having a streak
of yellow pattern.

As is my habit, I would make a minor change (I play a game of odd-man-out in
recursive mode with VBA) to the code Line and herein lies my doubt.

a) Sometimes when I make the change I would get the deadly message box
(vbokcancel) something on the following lines "Project needs to be RESET."

b) And rest of the times VBA would be very kind and would allow the change
in the code line, WITHOUT Resetting and I can continue with the code
execution (unless more errors pop up in the same line)


Whats the logic for the above behaviour. Can I predict in what kind of
changes , VBA would reset my project and when it would not.

Please guide me.

Thanks a lot,
Hari
India

F8 and Yellow pattern for compile error
 

Hari,

I see you have got no replies to this, so I will take a shot.

You mention recursive mode. I am not absolutely clear what you mean by this,
but does this mean that your code uses recursion. Are you handling the
recursion exits properly, not choking up the stack?

--

HTH

RP
(remove nothere from the email address if mailing direct)


"Hari Prasadh" wrote in message
...
Hi,

When I get an error, the offending line in my code would be having a
streak
of yellow pattern.

As is my habit, I would make a minor change (I play a game of odd-man-out
in
recursive mode with VBA) to the code Line and herein lies my doubt.

a) Sometimes when I make the change I would get the deadly message box
(vbokcancel) something on the following lines "Project needs to be RESET."

b) And rest of the times VBA would be very kind and would allow the change
in the code line, WITHOUT Resetting and I can continue with the code
execution (unless more errors pop up in the same line)


Whats the logic for the above behaviour. Can I predict in what kind of
changes , VBA would reset my project and when it would not.

Please guide me.

Thanks a lot,
Hari
India

F8 and Yellow pattern for compile error
 

Hi Bob,

Im sorry, I used *recursion* word as a pun.

I mean I find it very hard to debug the error. So, when-ever there is a
yellow line, I would change a small detail within that ( remember my
yesterday's post regarding "Cleaning up the syntax" where I was at my wit's
end and I provided 3 variations -- a) , b) , c) -- of changes I tried) and
see whether it works. So in effect I keep *permuting* the various possible
*syntaxes*.

Now when Iam playing this *game* sometimes VBA would reset my project and
sometimes its very graceful and allows with the continuation of the rest of
the code.

I wanted to *predict* when VBA would reset and when it wouldnt.

Thanks a lot,
Hari
India

"Bob Phillips" wrote in message
...
Hari,

I see you have got no replies to this, so I will take a shot.

You mention recursive mode. I am not absolutely clear what you mean by
this,
but does this mean that your code uses recursion. Are you handling the
recursion exits properly, not choking up the stack?

--

HTH

RP
(remove nothere from the email address if mailing direct)


"Hari Prasadh" wrote in message
...
Hi,

When I get an error, the offending line in my code would be having a
streak
of yellow pattern.

As is my habit, I would make a minor change (I play a game of odd-man-out
in
recursive mode with VBA) to the code Line and herein lies my doubt.

a) Sometimes when I make the change I would get the deadly message box
(vbokcancel) something on the following lines "Project needs to be
RESET."

b) And rest of the times VBA would be very kind and would allow the
change
in the code line, WITHOUT Resetting and I can continue with the code
execution (unless more errors pop up in the same line)


Whats the logic for the above behaviour. Can I predict in what kind of
changes , VBA would reset my project and when it would not.

Please guide me.

Thanks a lot,
Hari
India

F8 and Yellow pattern for compile error
 

LOL.

I though odd-man-out was some game that you were writing in VBA, using
recursive routine calls.

Sorry, I can't offer any help here off the top, I think it is one of those
things you need to be standing there to see it happen. Now, if you want to
fly me over to Delhi to take a look ... ;-).

Best of luck

Bob


"Hari Prasadh" wrote in message
...
Hi Bob,

Im sorry, I used *recursion* word as a pun.

I mean I find it very hard to debug the error. So, when-ever there is a
yellow line, I would change a small detail within that ( remember my
yesterday's post regarding "Cleaning up the syntax" where I was at my
wit's
end and I provided 3 variations -- a) , b) , c) -- of changes I tried)
and
see whether it works. So in effect I keep *permuting* the various possible
*syntaxes*.

Now when Iam playing this *game* sometimes VBA would reset my project and
sometimes its very graceful and allows with the continuation of the rest
of
the code.

I wanted to *predict* when VBA would reset and when it wouldnt.

Thanks a lot,
Hari
India

"Bob Phillips" wrote in message
...
Hari,

I see you have got no replies to this, so I will take a shot.

You mention recursive mode. I am not absolutely clear what you mean by
this,
but does this mean that your code uses recursion. Are you handling the
recursion exits properly, not choking up the stack?

--

HTH

RP
(remove nothere from the email address if mailing direct)


"Hari Prasadh" wrote in message
...
Hi,

When I get an error, the offending line in my code would be having a
streak
of yellow pattern.

As is my habit, I would make a minor change (I play a game of
odd-man-out
in
recursive mode with VBA) to the code Line and herein lies my doubt.

a) Sometimes when I make the change I would get the deadly message box
(vbokcancel) something on the following lines "Project needs to be
RESET."

b) And rest of the times VBA would be very kind and would allow the
change
in the code line, WITHOUT Resetting and I can continue with the code
execution (unless more errors pop up in the same line)


Whats the logic for the above behaviour. Can I predict in what kind of
changes , VBA would reset my project and when it would not.

Please guide me.

Thanks a lot,
Hari
India

F8 and Yellow pattern for compile error
 

Hi Bob,

I though odd-man-out was some game that you were writing in VBA,...

I wish that I get on that *level* as soon as possible.

You're welcome to Delhi (and my place) anytime.

Thanks a lot,
Hari
India

"Bob Phillips" wrote in message
...
LOL.

I though odd-man-out was some game that you were writing in VBA, using
recursive routine calls.

Sorry, I can't offer any help here off the top, I think it is one of those
things you need to be standing there to see it happen. Now, if you want to
fly me over to Delhi to take a look ... ;-).

Best of luck

Bob