I don't know what you mean. ??? It sounds like you're taking a jab at me. < scratching my head >

Like I said before I'm a VFP developer. You don't need to jab at me.

I don't know what it's like in your realm. But I'm self-employed and have made a good living from the Fox for about 15 years. For me personally, it's disappointing to know that such a competitive weapon in the IT world is not moving forward any longer. Microsoft has parked the product in the museum of history. (Or hidden it in a back lot, depending on how you want to look at it.)

I stepped into this thread because of another post and suggested that a customer's concern over VFP might have nothing to do with the skills or trust-level for a specific developer. But rather, the mindset that the decision-maker has toward VFP and long-term support of an app if the original developer is nowhere to be found a few years from now.

I didn't mean to raise anyone's ire about VFP. You know, in some environments maybe no one has a second thought or concern if you propose a new project be done in VFP. Great! But the more time goes by, the more friction and concern we're likely to encounter when suggesting VFP development. If we're having a difficult time trying to persuade a customer (or employer) right now about VFP, imagine the degree of difficulty 5 years now as we try to make such an argument.

My original post was suggesting that smart-thinking business managers are naturally wondering beyond the immediacy of a solution that someone can provide this month or this year. They're also wondering about complications or flexibility they'll have a few years from now.

The original question on this thread comes because of some manager's anxiety about the future.

I'm not arguing for, or against, VFP. I was trying to point out that if anyone is finding it hard now to persuade a customer that VFP is a good choice, then:

1) understand that it is natural, given the circumstances of VFP, and
2) think about it from the eyes of the customer and be prepared to comfort their concerns. (And one of their concerns may be... just may be... the difficulty of finding quality people in case the original developer disappears.)

If one can discuss VFP from a balanced viewpoint and ease the concerns of management, then they've got a much better chance of getting approval on VFP work.

Contrast that with a business manager trying to have a discussion with a developer and the only thing coming out of the developer's mouth is VFP, VFP, VFP.

Again, I don't know what your environment is like. And maybe VFP fits 99% of everything in your world.... fine... congratulations. It's a blessing of sorts.

But for a lot of us, the art in what we do best for the customer is not the technical work. It's the careful listening and the follow through to solve business problems with whatever tool makes sense.

If that's preaching, then I guess I'm a preacher. <s>



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