I think that you nailed it Gord, I tested:

Sub test()
For x = 1 To 10000
Debug.Print x
Next x
End Sub

and although you can see all 10,000 numbers being printed to the Immediate
Window, only the last 195 - 199 numbers are available in the window. It
would seem therefore that the Immediate Window has a limit of displaying
only the last 200 or so printouts.

Testing with the Event Procedu

Private Sub Worksheet_Change(ByVal Target As Excel.Range)
Debug.Print Target.Value
Target.Value = UCase(Target.Value)
End Sub

and entering Chuck in any cell produced 199 CHUCK's *not* as I would have
expected, one Chuck and 198 CHUCK's, (because the Debug.Print was *before*
the UCase call). I therefore assume that VBA gives up after *more* then 200
cycles but displays only the last 200.

--
Sandy
In Perth, the ancient capital of Scotland
and the crowning place of kings


Replace @mailinator.com with @tiscali.co.uk


"Gord Dibben" <gorddibbATshawDOTca wrote in message
...
Not a clunk<g

Some limitation to debug?

Debug and the Immediate Window are uncharted waters for me.


Gord

On Thu, 26 Jul 2007 18:17:59 +0100, "Sandy Mann"

wrote:

Thank you for confiming it Gord. Have you got any idea why it fires only
65
times if you leave the original printouts in the Immediate Window?