>Hi George
>
>>>(3) The guy gets beaten up for saying that something is a bug. And it is, it clearly is
>>
>>Yes, it is a bug, but it has nothing to do with evaluating NULL but rather a problem with the call stack when an object reference is stored in a property with an _assign method more than twice. Take a look at my reply to Fabio.
>>
>>I wasn't beating anyone up. Simply a differing of opinion.
>
>I have to agree with you. You and Fabio seem to differ in your approaches. Neither is wrong, because even with proof, there is room for interpretation of the results.

Mike,

First of all thank you.

I'd like to say that this has nothing to do with who the original poster is. Am I always skeptical of a "BUG" post? Yes, and I think it's a good idea. I've run into too many cases where it's my own stupidity that causes a "BUG". Further, I believe in the scientific method. In this case, I, both unknowningly and unfortunately, didn't realize that I set a break point when I did my original tests. This allowed me to click the command button repeatedly without a noticable result. It was my mistake and I freely admit it.