Gerry,

>>Well, even doctors make errors. Why can't people give MSFT the same consideration. I surely don't want software to ship with bugs but it's a fact of life. Please let me know when the world is perfect.. <g>
>
>I have been using MS software since the early 80's (day 1). I have a Universal Subscription. I think I have "bitching rights".

*chuckle*

I've been programming with Fox products since 1986-7 and MS products since the late 70's so I think I do too, if we've swerved into a pi**ing contest. <g> I'm comfortable that you want to gripe and think you should if you think it'll help.

>
>I'm not talking about some "subtle" bug here; if you think that it's acceptable to not even verify one's own download, then we have a difference of opinion in terms of what constitutes due care /consideration / deliberation / whatever.

Bugs, small and great are not good. I think that the team is probably mortified this one slipped out - but that does happen - which is my point. My guess is that you won't say anything by griping that the team hasn't already said to themselves. <g> I just do not rely on even the VFP team's assertion that the product is ready. I'll test it myself for a while thankyouverymuch. <g> What I'm suggesting is that I need to take responsibility for making sure the product meets my client's needs, not MSFT. I think some here (not you) prefer that others think for them and are lazy about regression testing. It's easier to whine that do the heavy lifting.

>
>I was waiting for someone to defend the status quo; I didn't expect it to be you (even though we've had differing opinions).

<g>

I don't think I'm defending the status quo. I want bugs taken care of as soon as possible. I'm just suggesting that in the big scheme of things this isn't a huge deal. Perhaps time will prove me wrong but I don't think so. For example, I think it would be irresponsible to immediately put a product out based on VFP7. I have given very specific and strong instructions to my developers that I want them to develop code (except menus) with VFP7 but all builds will be in 6.0 SP5 until we have reached a point of confidence. I think the new product is great but it seems to me that common sense dictates a settling out period before sending the product out into the field.


>
>I'm not perfect, but I strive to be ... when it comes to other people's / my Users' time. I will never accept that delivering buggy software "is a fact of live". I've made mistakes; but MS was never on the critical path ... this puppy could have at least installed properly.
>
>Bye.

Well, we certainly agree on this. That's why I'm ever so slowly going to introduce the new version. Perhaps that's why I'm not too concerned that a noticeable bug slipped out. In my mind I know the VFP team will fix it and I have the luxury of deciding when to deploy a VFP7-based solution.

I just dont' see why this is a real big deal I guess. Perhaps others aren't as careful as I am?