For your information, I am not, never have been, and never will be an MVP.

As for the rest, in all of 2002 so far, running VFP 7 on Win 2K, all promptly patched, on an IBM Thinkpad laptop 10-12 hours per day, I have had exactly two crashes.

Reliability-wise, VFP is currently way beyond my wildest dreams of yesteryear, and moreover it's way better than everything else in its class.

Like I said, people who are running on shit hardware and on home-edition os'es, then that's another issue, more reliably solved at source, not in Redmond.

**--** Steve




>Well isn't that special.
>
>Now we have an esteemed MVP essentially saying that the 75+ bugs reported here for VFP7 are essentially a product of poor developer practises and/or poor quality operating environments.
>
>Even if they were (which you most assuredly know is not the case) MS elected to sell VFP to the masses and they, more than anyone else, know precisely what that entails in terms of potential support issues. Non-programmers will buy it and it will be run on antiquated gear with old and unmaintained OSes and old drivers and faulty peripherals.
>
>Reminds me of another who stated that VFP7 was essentially C000005-free. Then SP1 came out, fixing several.
>
>And in any case, why does this qualify current bug reporting/publication practises as acceptable in any way???
>
>You guys need to be more in touch with "the community".
>
>
>>Me too. My mean time between VFP errors is measured in weeks, if not months. Not to say problems don't exist, but the combination of good hardware, good OS (NT 4+latest SP or Win 2K), and not trusting most ActiveX controls from any source means virtually zero problems.
>>
>>**--** Steve
>>
>>
>>>Really? Wow. I don't remember the last time I had problems in VFP (and I use it everyday, all day) that I lost time or work due to a FoxPro bug.
>>>

>>>And I do a lot of stupid stuff with VFP. If anything, I get a C5 here or there and testing, then I find someway to take care of it.