I'm very sorry, but I don't understand what you're saying here at all.
It's my fault, I'm sure, but perhaps if you could rephrase or if someone else could help me understand, I'd be happy to reply.


Sorry, but this is a my fault.

I explain the "bug on the bugs" process:

- VFP v.3.0 have not a bug X
- VFP v.5.0 have the bug X
- now VFPT it receives several signallings for Bug X
- VFP v.6.0 is released with the bug X not fixed
- Now MS VFPT it publishes the description of bug X in VFP 5/6
- now various experts on VFP community read the article, found workarounds, etc.
- VFP v.7.0 is released with the bug X not fixed
- now various experts check for Bug X, -> it is not fixed ! -> the bug is fossilized in the mind
- VFP v.8.0 is released with the bug X not fixed
- VFP 8.0 sp1 is released with the bug X fixed
- now, the MS VFPT article is not audited up-to-date

Result :

A developer read the article,what must he think?
VFP 7 has bug X ?
VFP 8 has bug X ?
The new service pack has bug X ?

For every new release or service pack we must retest all the bugs remained in the limbo?

When ( like example ) a developer put a code example on UT,
and this contains bug X, naturally one expert it marks it bug X,
but this fact depends on the used version, but the version where bug X has been fixed is not published.

The result is one crazy confusion.

Nancy, I remain astounded in thinking next to how many hours forgiveness in the community in order to take place all this.

But by now I have understood it, mine is alone utopy.

VFP documentation does not have not even the release where a command is supported!
I can think that there is documentation on which version has a bug or not?

Hello Nancy.

Fabio