>Like what? What is a higher priority than having your product work like it should?

Some customers may be anxiously awaiting features that have already been shown in Europa and would rather have them than a fix to this bug.

>
>>At what point should the Fox team stop fixing bugs and issue the SP? How many and which bugs should be fixed in the SP? You want this array problem fixed. It may not affect others and they want something else fixed that doesn't affect you. Let's say that the VFP team can only fix one of the two? Which one is it? What if they do decide to fix those two bugs and bug one takes an hour to fix your bug, but it takes a month for bug two? Are you willing to wait the extra month to get your fix (again, keeping in mind you are one data point)?
>
>You are just stating the obvious. M$ are patching stuff all the time. My PC nearly everyday tells me that there are new patches, fixes, hotfixes and downloads for virtually everything M$ on my system.

1. The Windows team is MUCH bigger than the Fox team and thus can support debugging and testing these fixes.
2. The problems affect a MUCH larger customer base than VFP.
3. Not all bugs with Windows are fixed in the patches, fixes, hotfixes, and downloads. Some wait for the next version to be released.

>Why not VFP? Why doesn't your logic apply to everything else M$ patches on an almost daily basis? Coz its just about profile - they can't get away with it on mainstream products but they seemingly can jerk VFP user around? Now Craig, lets see how you defend M$ on this point?

You say the array issue was posted yesterday. Here you are already loudly complaining about it. Give the Fox team the opportunity to determine the impact, track down the bug, squash it, test it, create the SP, test it, post it. It isn't going to happen in one day. The patches, fixes, hotfixes, and downloads you referred to earlier sometimes have taken months of work to resolve.

And, FYI, I am not defending MS on anything. I'm simply stating the facts as they exist for the entire industry. Oracle, IBM, Borland, Symantec, etc all develop software using the same cost/benefit analysis.

>
>>At what point should work on an SP stop and work start on Europa?
>
>I think most businesses would prefer to have something completed correctly before starting on the "next thing". Maybe they should downtools on Europa until the product they are selling now works as it should.

Are you saying that EVERY known defect in VFP8 should be fixed before starting on Europa? If so, we will never get Europa.

>We are not 18-24 months into VFP8 and Europa is just around the corner. VFP8 has just been released and there seems to be an alarming number of issues cropping up at this early stage. If a bug was discovered a few months before a new product release, then sure, wait for the next one. But touting Europa as a reason to not fix VFP8 bugs now it poppycock, plain and simple.

This same arguement was made for VFP6 and VFP7. It just doesn't hold water.