Well, I didn't say they don't love it. It does seem to me that - from what I can tell - Calvin does enjoy VFP greatly (not to leave out anyone else, I just don't have as much "data" on them). What my last statement was actually saying is just that when people are stretched thin, they can't do their best work. I was adding in that they may be very interested in the new frontiers in .NET, but didn't mean to say they have developed a distaste for VFP.

I have a problem with what M$ did to VFP. But that is not directed at the developers at all. The developers, and the team in general, put out one great version after another. My displeasure is directed at upper mgt.

>I disagree with your last statement. The devs love VFP.
>
>>Automated testing is a great help, I have no doubt. But wouldn't you say it can also be a crutch?
>>
>>There have been UI issues that have made the UI harder to work with. One is the propensity for the Properties sheet to be a focus hog. It used to be that you could count on the Command window retaining focus when it should. Since VFP 8, I've found myself constantly having to click on the Command window because it has lost focus when it shouldn't have. Usually focus goes to the Properties sheet. There are other focus issues that add mouse clicks and keystrokes not previously necessary.
>>
>>There are bugs in the software and bugs come from those writing the software, not just out of thin air. I know those guys are excellent programmers, but I stand by my statement that when people are stretched thin (not to mentioned probably being very interested in the new frontiers found in .NET and less interested in VFP), they are not doing their best work.
>>
>>
>>>VFP testing has been largely automated for quite some time; there are about 4000 tests that are run for each OS/Language combo in a full test pass. Automated testing is great - before I left I had it where you went to a web page, selected a bank of machines and a series of tests and off you went. So automation allowed us to run a huge number of tests with minimal effort.
>>>
>>>My understanding is that these test runs were done for SP2. The guy I trained as my replacement moved on so I don't have any direct test contacts anymore.
>>>
>>>Now, one observation I think may have a bearing. The most difficult thing to test is UI because it's all "mechanical turk" stuff and very difficult to automate. If you don't have a large testing staff it's quite easy to miss UI issues.
>>>
>>>Something else - Calvin, Aleksey, and Richard could code VFP in their sleep. None of those guys are prone to checking in buggy code no matter how many other tasks they have.