I appreciate the support, Mike.

That might work, but it does depend on the good will of the community and, most importantly, still leaves us totally in the dark as to its real status within MS.

Sure, it might provide proof-positive that MS is failing us miserably. We have that proof already - lots of bugs got "worked" to the point of reproducibility by Jim Saunder and/or Mike Stewart and/or John Koziol, yet they remain unlisted in the MS KB.

In addition, bugs arrive at MS from sources all over the place, reported by people who do not frequent the UT or Wiki or... These would continue to be unknown to us here.

This really is a MS problem - it is THEIR bug database that has the information. We should help here (UT) in any way that we can, but it really is up to MS to provide the information andkeep us updated.

Of course, if MS (the VFP Team in particular) wanted to "offload" this to some other entity then the UT could well become the OFFICIAL place to report VFP bugs, but the VFP Team would still have to participate and it would of course be necessary to expose the existing list so that this could be done comprehensively.

I know this - the existing "system" isn't worth the HTML used to provide it. We, the VFP community, deserve better.

Jim

>Hi George
>
>I share Jim's frustration, and I'm certain many have felt like Jim at one time or another. I believe your points are correct and logical. However, wouldn't it be a good thing for VFP if there was a way for VFP users to
>
>1) report a bug
>2) refine the report until its perfectly reproducible by others
>3) allow others to post demonstrable work-arounds
>4) submit it to MS
>
>If so, then how could such a system be started?
>
>>>Hi Sergey,
>>>
>>>Thanks for the tip. I wasted so much time on this
>>>issue.
>>>
>>Rich,
>>
>>The other respondant to your post gave you, IMO, some very, very bad advice.
>>
>>Point one, the UT is not the sole forum for information about VFP. There are others. Just because the poster wasn't aware of the problem, doesn't mean that others aren't.
>>
>>Point two, it takes considerable time for an article to show up in the MS KB. This time lag is due strictly to the procedures that Product Support has to go through in order to get a KB article published, even one as simple as this.
>>
>>Point three, the KB is very useful. You do, however, know how to use it and describe the problem. I wouldn't do without it.
>>
>>Point four, and probably from mutual experience, if you can't re-produce a problem, you can't fix it.
>>
>>Point five, the VFP team has no control over the corporate policy at Microsoft. This means that bugs that they find have to go through exactly the same process that bugs in other products do.
>>
>>Point six, contrary to the other poster, I'd encourage you to not only report bugs, but provide as much additional information as you possibly can to help re-produce it. Not doing so is "shooting yourself in the foot". You've done nothing to fix the problem and you've provided no assitance to others who may experience the same.