Ah, I understand now - you were looking to preach, not get advice, in your original message.


>I understand your point about COBOL. It also runs on Linux and Mac.
>
>But, predictably, only large businesses who have already dumped massive investments into COBOL will continue to use it. You just don't find it in a majority of businesses.
>
>It seems obvious and self-explanatory that VB6 developers will be finding it harder and harder to justify new projects in VB6. Not that it doesn't happen. But I'd bet they're finding it more difficult to be persuasive and to win the argument. It's the same dynamic for VFP developers.
>
>Remember, I am one of them.
>
>Fact #1, VB6 is a fine tool. You can build professional apps with it.
>Fact #2, VFP9 is a great tool! You can build professional apps with it.
>Fact #3, They've both peaked. They both face dwindling usage.
>
>For you, or I, or anyone else to pitch VFP as a solution, we need to recognize that the business world will be balancing fact #2 against fact #3. That's all I'm saying.
>
>No need to sing to the choir. The persuasion needs to be with the customer. I'm just saying it behooves us to understand the mindset of the customer (and make sure we're not in denial about the reality of the marketplace).
>
>Guy
>
>
>
>
>
>
>
>
>
>
>>Bad example, at least for me and my opinion of FPW.
>>
>>By the by, COBOL came off the mainframe almost 10 years ago and has its own .Net plugins.
>>
>>But, to use your own logic, if all they're interested in is mainstream servers, databases and Windows (oh MY!) then have your VFP frontend go to a SQL backend. That will satisfy probably 80% of the 'IT' people out there.
>>
>>Or, you could just ask them how many VB6 applications they have running. What you say that businesses wouldn't do any more new development in VB6? You'd be surprised, and so would they.
>>