Hi Tom:

Nice insights. To hell with it working correctly - just get the next one out of the door <s>.

>Hello Gary;
>
>“Leaving The Box” (Visual Studio that is) allows the VFP team to concentrate on the “next version of the product”! No time or money for marketing, or bug fixes – just push out the “next version”. If old code that worked is broken in a new version who cares? It is the “new features we adore”. We are told that VFP uses a “test plan or script”. I would suggest the “script” should be reviewed. Woops! No time for that – just crank out that next version!
>
>I do know what SQA is! Software Quality Assurance is what it means in Silicon Valley. Who needs quality when you have the market?
>
>We must sound like ingrates if we dare to criticize VFP! After all, do you expect the product to work the way you think it should? That it works at all is commendable. Still I have this dream that VFP will approach perfection. If there is a problem with VFP just tell the client, “Just wait for the next version! It will have more features”!
>
>I hope that no one from the VFP development team reads this post or ones like it. After all, we want them to spend all his/her time delivering another wonderful new version of our beloved VFP.
>
>Why do I think I would rather sell nails in a small hardware store in a small community where the word “technology” means the Model T Ford? :)
>
>Tom
>
>
>
>>>Can you name any commercially available application with the distribution numbers or complexity of VFP that doesn't have the bug count increase after it's released? I don't think the number of reported bugs affects the decision to produce a service pack. It is more dependent on how serious the bugs are.
>>
>>I'm not sure how many made the kind of claims that were made about VFP8 prior to release.
>>
>>>>I notice over on the WWWC board, Randy Pearson has repro'd a serious bug with the collection class. He has found problems using object references via FOR EACH (this was a similar problem with my automation bug in VFP7). His answer ... use FOR i = 1 to collection.count. For a much touted feature where one of the advantages was being able to process the collection with a FOR EACH, to find this is buggy is a bit of a poor show.
>>>
>>>This alone won't justify an SP. MS must determine how many users are affected, is there a workaround, how many resources are required to fix it, etc. Remember...at this point, anything fixed in an SP must be fixed twice. Once in the SP and once in the Europa code base.
>>
>>You must be kidding? A major feature like the collection class where the ability to run FOR EACH doesn't function correctly? You think this is acceptable? You don't think this requires an interim fix? Jeez, in my own collection class (based on an array), I can directly spin through the array using FOR EACH and correctly utilise any object references that exist. But you can't do this correctly in the new collection class??? And there's no point in fixing it in VFP8 because it will need to be fixed in Europa too? So what? Whatever happened to VFP leaving the Visual Studio fold so that the team could be more responsive, release things more quickly etc.,
>>
>>Things like this need to be fixed to win the confidence of users of the latest version and for them to know that when they get the next version, issues will be corrected promptly too. There is nothing worse than upgrading and finding that new features don't work as advertised and running code breaks.
>>
>>Sorry Craig but I think you are standing up for M$ a little too much on this occasion.