>I'm wondering about the stability of VFP 9. I couldn't say it's unstable, but then I couldn't say it's any more stable than VFP 8. Since the days of VFP 5, they have solved stability issues (I'm sure we all remember the dreaded C0000005 errors). However, what I've noticed in VFP 9 is that it has a much greater tendancy to lock up during a compile. This happens across all my projects, but, of course, I see it in the projects in which I work most of the time. In fact, I just stopped typing this for a second to End Task on VFP because it had locked up during a build. This was a rare event in VFP 8, but since I've started using VFP 9 it's happening too frequently (it happened twice today already).
>
>John Koziol (sp?) has said how stable it is. Well, maybe, but some of the things he uses to support this are not necessarily valid. He says the number of user reported issues (I can't think of the exact wording he used) has dropped drastically. Well, I'd like to hear some details on that. This may or may not be reliable since we've had a lot of people abandoning the ship. That being the case, you'd expect reports to drop off. Also, he talks alot about the automated testing tools. Well, that's not valid if the tests aren't. I can write some tests that my programs could run all day long without a glitch, but that doesn't mean that there's not a bug in there that is simply not found by any of the tests. And just because he was lead tester (in reality, if not in title), I am certainly not blaming him. Quality (or lack thereof) is the result of a team effort (or lack thereof). It's not to be attributed to or blamed on any one person (unless it's a one-person team, that is <g>).
>
>Then there are the bugs that have been in the product for way too long that they simply ignore. Or the bugs that they refuse to recognize as bugs. Acknowledging and fixing some of these would help greatly.
>
>Before finishing, I must say that I have loved FoxPro for many a year now (since the FoxBase days) and have used it to great success, however that doesn't mean that it can't be improved. I wonder if the upcoming service pack will really address important issues or if it will just be a bunch of fluff and hype.
>
>Russell Campbell

You should open "debug output" during the build process.