Hi george,

While I agree, that sending no bugsreport would only make thing worse, I'd really love to see some feedback about the status of the reported bug. If you'd look at the support you get from SEAGATE when you buy crystal reports, you can only draw the conclusion that if they can deliver some sort of support, MS could and should be either.

I agree with Jim, that its very frustrating that there is no feedback or whatsoever regarding reported bugs. Though I'm certainly aware that setting up a support team and defining terms and conditions is not an easy task, all is better than we have now.

Walter,

>>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.