Yeah, it seems that they have decided it's best to keep us in the dark. It used to be that you could get a bug list and a bug fix list. The bug list was helpful when you ran into something that didn't seem to be caused by your code. Were you facing a VFP bug (and was there a workaround) or should you keep looking at your code? The list is also helpful when you want to upgrade. What are the known bugs and do any of them amount to a show stopper for you? (A molehill to one application is a mountain to another.) I think it's a developer's responsibility to ensure that there are no bugs that will seriously affect his/her users, but MS has no desire to help you do this. They release absolutely no information for a "dot-oh" release.

The bug fix list was just good info so that you could confirm that something that you wanted fixed did get fixed. I did find some separate lists for that, but of course they like to publish that info. The bug list is something they want to keep under wraps.

Now they just try to hide all of this. And they say "it's the most stable version, yet." How do we know? Well, simply because they said it, that's how!

I did check out that bug list on the UT, but I could not find the bug that I'm dealing with and I can't find a report of it (it's hard to describe in a few words, so therefore it is also hard to search for).

Thanks for your reply,

Russell


>Russell,
>
>The closest you'll probably find is the one that is a link in your message :) (Assuming you have autolinks turned on).
>
>MS doesn't publish a list of bugs for VFP.
>
>>Is there a centralized bug list for VFP 8? I am running into a problem that is hard to describe in just one sentence and so it is hard to search the KB or Googlle for it. I'd like to scan the known bug list, but MS seems to make that hard to find . . .
>>
>>Thanks,
>>
>>Russell Campbell