Thanks GB,

Okay I'll ask the user to open the VBE and in the immediate window
type: application.screenupdating = false - before they delete any
rows! <g

In all seriousness guys that is not the problem - well if it is I
don't think there's much I can do about it.

VBA code is not 'running' at this point. Objects are instantiated and
ready to offer up their properties if called on by a Sheet_Change
event but it is the user that is deleting rows not VBA.

When the user selects a large number of rows and right-clicks on a row
header and chooses 'Delete' the Sheet_Change event doesn't fire for
about 30 seconds while Excel does something in the background. In fact
I'm pretty sure no VBA code is running during that time.

Any uber OOPers out there? What happens when a user deletes one of
your objects without you having the chance to terminate it cleanly? Is
Excel just juggling/recovering memory?

Has anyone found a way to detect a 'Delete' event before the delete
happens? Is the only way round this to write a new 'Delete' menu item
for the "Row" shortcut menu item?