>>Where this change to design is documented?
>
>It doesn't matter.
>Haven't you learned, yet, that calling anything a bug brings out certain people to say otherwise regardless of the facts. They can just make up a new fact to suit the current situation.
>
>My guess is that it is because of this phenomenon that the VFP BUG List is very very very RARELY updated. This way the makers of the new rules get to set the new rules and then there is no need for a bug to be declared.

Look, Nelson, if you have something to say to me, at least give me the courtesy and have the courage to say it to my face.

Fact of the matter is that neither of us can say with the slightest degree of certitude one way or another. Rather than insulting me (which I take your post as regardless of any statement by you to the contrary), it would be far better for you just to express your own opinion.

Mine was based on the significant difference between the behaviors in the two versions. As I said, from the appearance would have been made with knowledge of forethought. It could be, however, that in correcting the bug that was documented in MSKB#Q247494, that this "feature" crept in.

The only folks that can say for certain are those who work on the product and have access to the source code. That's the bottom line, and there's no argument that you can present to the contrary.

EOT