>>Still more serious it is to release a new product, like VFP9,
>>without the DETAILED list of all the fixed bugs.
>>
>>Every correct bug can change the behavior of the application.
>>
>>I still do not have an application much extending,
>>But without a list of the made variations,
>>I would be paralyzed from the idea to use a new package
>>of which I cannot know the modifications.
>
>Please refer to the KB articles below...
>
>Miscellaneous problems that are fixed by Visual FoxPro 9.0
>http://support.microsoft.com/kb/894011/EN-US/
>
>Memory leak and corruption bugs that are fixed in Visual FoxPro 9.0
>http://support.microsoft.com/kb/894010/EN-US/

Hi Ken,
a example:
Fixed corruption bugs

• Incorrect results are returned from a query when the NOT operator is applied to a sub-query comparison.
• Incorrect results are returned from a query when a temporary index on a nullable field is used to optimize a JOIN evaluation. 
......
• Incorrect results are returned from a query when the NOT operator is applied to a sub-query comparison. 
......
• Incorrect results are returned from a query when a temporary index on a nullable field is used to optimize JOIN evaluation. 


Now, or this is a write error, or exists two bugs with the same description !
I guess that the second is the true.

Another

• Incorrect results are returned from a query when null values are involved in sub-query comparison. 

Involved ? Where ? How ? What ?

If i have a application, how can i check it with this informations ?

Now, with the quality of the information supplied, the result is only one: 
 anxiety 

Then, is of agreement with you, better not to publish nothing.

Fabio