>>Thanks for letting me know your opinion/assumptions, I appreciate this. The fact that you preferred not to answer my question is, actually, a pretty good answer itself. Anything that can be said about that situation may hurt feelings. I agree, no one likes to be pointed to his/hers mistakes. One can choose not to say anything, but that doesn't change and doesn't make go away what happened.
>
>I'm not sure what you're reading into the fact that I did not directly answer the question. In fact, I did not see the question as sincere, but rather another opportunity to hurl another insult to James and perhaps others who might dare to disagree. I did address the question from that perspective. But, if you'd like a more direct answer, you could have left much of your response as it was, with the exception being the question "Did you blindly rely on this ... or did you simply not think ..." This part of your response was unnecessary and only added insult. Further, it would have been a nice touch to explain why the change was made without having to be asked for it.
>

Hi Del,

I read exactly what you've described here. I.e. I could refrain from expressing my opinion. But I chose not to. The opinion wasn't pleasing, but I still believe it was true. One way to handle not pleasing feedback is to become or appear insulted, there are more useful ways.

>IAC, I agree with James on the point that it would have been nice to have control over this behavior with a setting of some sort. Regardless, we will adapt as necessary.

I really hate to point this out, but James's application had a bug long before it was upgraded to VFP9. The app was pretending to refresh data. New behavior made that bug clearly visible, whereas the setting would just allow it to "bloom". At the end, James's customer got an app that actually does what it is supposed to do.

Thanks,
Aleksey.