am just relaying what one engineer said as to how it worked. They are not
CS guys and I am not sure he knew what he was talking about. I think he
meant 2 of the ~80 values get done 2 times if certain conditions are met.
If that is true then it would stay inside the routine that is called from
the sheet_change event.

No I can't assume a last cell. They knew nothing of the benefits of a real
table.

I found one thing that seemed to make a difference. I had not set the
sheet that I takes/displays the data the active sheet. After I did that
thru code, I could also not get it to fail.

I have given them 2 choices, a delay loop around a DoEvents, or use their
global variable that they already had (I choose not to use it originally).


"Sharad" wrote in message
...
Does this works even if the displayed results on the screen is slow
due to
video speed

Yes, because it has nothing to do with processor or vedio speed.

which may call itself 2 times.
Now this could be the problem. Do you mean that the after you write
data to the cell, when it fires the event, it may call that event
(worksheet_change) 2 times before you want to procede further?
If yes, are you sure that it will always call 2 times, or say awlays a
'n' number of times?

Or atleast do you know te address of the last cell that will change,
before you want to procede? If yes, then you can set 'canInow = True' in
the event of the last cell that you know will change.
But it that cell does not change, you will land up in an infinite loop,
excel will just hang, unless you press 'Ctrl+Break'.

Sharad

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!