>Cannot say I envy you with this situation
>
>
>If you are out of ideas - you may want to change the code in the error handler. Assuming that the memory may already be corrupt before getting to the error handler may make sense - but you really don't know - do you ?
>
>I've had cases where changing the value of editboxes (in the keypress event) errors out on C0000005 once in a while. Why ? I couldn't tell
>I've solved that one by replace controlsource wuth newvalue, followed by editbox.Refresh(). Same result but by another means
>
>I've had cases where I had to take DoDefault() out of the programmaticChange() - Error C0000005 once in a while
>
>So, changing the code of the error handler is not likely to solve the problem, but there's a chance it may - even if the memory was already corrupt it may not bomb out there
>

I've commented out this part of the error handler. I can't think of another way to get memory contents.

Tamar