>>Well I can say that I and many others are not.

>This is typical in arguments where you pad your argument to support your viewpoint. You cannot speak for anyone other than yourself unless you a part of a consortium to change the way bug reporting is handled.

Aren't you doing the same in saying that YOU are comfortable with it? I see room for improvement. You dismiss the opportunity for improvement.

>I don't worry about the bugs in VFP. In 15 years of fox and VFP development, I have NEVER run into a complete show stopper.

Well, nice for you. I've run into multiple problems that caused me a hell lot of work to workarround the issue. An example is that the AfterrowcolChange event does not fire when a refresh is somewhere in the chain between a beforerowcolchange and the afterrowcolchange. This bug suddenly appeared in VFP8SP1 and was a showstopper becuase the data on my form which had to be refreshed on the afterrowcolchange did not work anymore. I had to workarround the issue with timers etc. A very messy solution but in the end after several days of testing and rethinking the problem I circumvented the problem.

Another one, was supporting an application on Terminal Serivices and Citrix diplaying photos. While photos where displayed acceptable in a VFP7 picture control, the same control did not display it acceptable in VFP8. How I'm going to sell that to clients? The solution was to buy a 3rd party control, playing with it for several days in order to display the pictures decent agian. And depite the fact that I reported the bug well before the end of the BETA period of VFP8 is still exists in VFP8SP1.

And what to think about the issue where hidden columns in a grid causes visual anomalities. I posted the bug publically, Jim Saunders confirmed the bug and provided a workarround. All this was done on the UT so that everyone struggling with the very same problem:
a. Could confirm it is a know bug.
b. That there is a workarround you can inmediately use.

Based on this very positive experience I fight for publically posting bugs and workarrounds..


>There is always a work around. So to have these bugs posted, which will cause the real testers much aggravation in posting in multiple forums to please a few people, is counter-productive to the bug fix cycle.

I never spoke of posting it on multiple forums. And BTW this would give anyone the opportunity to find those workarrounds. It can save a whole lot of time for the ones who are dealing with the very same problem. I would be perfectly happy with a solution where those testers are only publishing their bugs here on the UT, we openly discuss it, and someone else posting it to MS.
I recognize that beta testers and regular bugreporting require slightly different approaches, but the goal stays the same: Make bugs public.

At least then everyone can track bugs and problems.

Walter,