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.


>Good question. But I would venture to guess there's an important difference between the COBOL world and the VFP world.
>
>COBOL is not in the mainstream of technology for most business. Yes, it sure is important if you're world is large scale computing and you have a massive investment in massive mainframes and the like. Maybe your environment is so large that you'll train whoever comes off the street (so-to-speak) and make your own talent.
>
>But most business environments are not that large. Instead, they are looking at mainstream servers and databases (and MS Windows), and want fast and reliable solutions with a good shot at talent that is commonly available if and when they need it.
>
>VFP enjoyed a time in the mainstream computing world. It was, and still is, and excellent product! VFP developers are often some of the best application developers that can be found anywhere. But that doesn't change the mindset of many businesses who wrestle with the question of what language or tool set should our new solution be based on?
>
>Look at the question another way (and forgive me for the exaggerated point). Let's say you are a business manager and you need a application developed to do "XYZ." Someone referred a good developer to you and you engage him to do a proof of concept for you. He comes back showing off his great example... written in FPW2.6.
>
>Take a moment and ask yourself some soul searching questions. (seriously)
>
>Does the developer have a good reputation? Let's say, Yes!
>Will the application do the job? Let's say, Yes!
>Are you excited about this new app going down this path?
>
>hmmmmmmm...
>
>
>
>
>
>
>
>>I'll see that argument and respond with "Where do the new COBOL programmers come from?"
>>
>>
>>>>In this case they simple don't trust you or your ability to support them in a future. I don't think you can do much about that.
>>>
>>>But also not to be taken so personally...
>>>
>>>The reality a business manager must struggle with is: the dwindling pool of talent of VFP expertise as the years go by, balanced against a growing pool of talent for other/newer languages or platforms.
>>>
>>>Finding good employees or contractors is a project in and of itself. It's not necessarily the person who is writing a solution right now that worries management. It's.. who will be dealing with it in the future if my guy gets hit by a bus?
>>>
>>>Guy