>I can't tell you how many bugs REPORTED HERE - and reproduced here by MS VFP personnel and entered into their database of bugs (as this one was) - simply do not show up in the MS KB.
>
>That is part 1 of this serious support problem.
>
>Part 2, of course, is that before the MS KB can be useful to you you essentially have to find out what your problem is. IF it's listed you may find a workaround. However, as noted above, you likely will not find it listed.
>
>Part 3 is that the MS bug reporting facility leaves no place for a bug reported to leave their name and contact information. We all know that with 5+ different operating systems, even more versions of Internet Explorer (which is tangled into EVERYTHING), varying combinations of OS components installed, countless different drivers for hardware and software in use, etc. etc. AND so many permutations and combinations of environments within VFP itself, chances are excellent that MS will not be able to reproduce a problem so THEY WILL DROP IT.
>No notice to the reporter (how can they) and no report database where we can otherwise look to see what people have been reporting.
>
>All this means that you and I and thousands of others have to WASTE tons of time re-finding bugs/solutions that are already well known.
>
>As long as MS continues this lop-sided practise I refuse to submit any bugs to them - there simply is no return at all!
>
>When MS adopts its major plank for pulling VFP OUT of the Visual Studio box - that VFP can 'go its own way, in its own way' - then I will reconsider my position.
>
>I encourage everyone to stop reporting their bugs to the MS VFP Team until the MS VFP Team agrees to provide some form of feedback on bugs ALL reported.

While I understand the frustration that leads you to that opinion, I think it's the wrong one. If fewer bugs are reported, then they will have no incentive to adjust their stance on it. I suggest the opposite: Repeatedly report the 'bug' in their ability to handle bug reports. Hopefully a few thousand reports of that repeatable bug will encourage them to spend some time correcting it for Service Pack 2. ;)