I wonder what would be the effect if every programmer refused to fix bugs because it might introduce new bugs in the process? :o)


>Hi Andrzej,
>
>>But still, workaround is not a fix.
>
>True, but who is going to fix it? The same team that gave us SP2? I suppose it would be a fraction of the SP2 team? If somehow we forced MS to fix these handful of SP2 issues I would expect the earliest we would see them is in an SP3 in about a year or more and after the SP2 team hasn't looked at/touched the code in months or done any testing in months. Don't get me wrong, I have nothing but respect for Calvin and the other VFP team members, but I don't think they have the infastructure in place anymore to release another polished version like we have become accustomed to. Unless I see evidence to the contrary, I still believe that more issues could be introduced by "fixing" SP2 issues.
>
>>What about bugs with WebServices and dead Toolbar in Report Preview?
>
>These are in XSource and we as a community can address these issues. I would be glad to tackle them but it will have to wait until I finish my current commitments.
>
>>BTW nice euphemism "issue" is just about bug, isn't it?
>
>I would say anything that prevents one from upgrading is an "issue". There are "issues" that were found with SP2 that are not considered "bugs". For example see Colin's comments about "ReportListener.vcx breaks SP1 reports" at http://fox.wikis.com/wc.dll?Wiki~VFP9SP2BugList~Wiki
>
>>Or maybe the best workaround is to stick with SP1, I suppose.
>
>I can see why some would want to do that. But I think we need to decide as a community, which runtime DLLs take precedent in the Common Files\VFP folder. I don't want an application using SP1 to force overwrite SP2 DLLs, with a higher version number, that my installer put in the Common Files\VFP folder. My opinion is, if you decide to stay with SP1 you should place your files into a non-common area.
>
>I would encourage anyone to carefully consider their choice to NOT upgrade to SP2. I realize these new issues are fustrating but look at the fix list posted at http://www.microsoft.com/downloads/details.aspx?familyid=A28DDEC6-BA3C-49D0-8176-8C0B3FCA06D1&displaylang=en . I count 138 fixes in SP2. I only count 11 issues at http://fox.wikis.com/wc.dll?Wiki~VFP9SP2BugList~Wiki and of those 11 at least 5 we have access to the source code and we can fix ourselves and I think 2 others were bugs that were there all along, not necessarily introduced in SP2. And I think we currently have workarounds for 2 of the remaining 4.
>
>Am I missing something? Trading 138 fixes for 2-11 bugs seems like a no-brainer. Unless of course you have a genuine reason not to upgrade after evaluating the product. It just seems to me that many people are refusing to upgrade because of comments made about SP2 and not because they have actually evaluated it.