Everyone - thanks for the links and ideas, they're helpful. I still have to figure out how to distill all of this info. It seems I almost need to different versions - one for tech. people, and one for business people.

Or, in addition to "Why", maybe I should come up with a list of the common misconceptions about VFP and argue each point (maybe I should have named this thread, "Why NOT VFP"). Let's see:

- Isn't FoxPro dead?
- Isn't it an outdated language (like COBOL)?
- File-based databases suck because (fill in any reason).
- I've got a friend who says VFP x is the last version.
- If it's not part of .NET, that means it's (dead/not supported/etc).
- I've got a friend who's company had a VFP project crash and burn, therefore, VFP is bad (who is this "friend" and where can I meet him/her to slap some sense into them??)
- .NET is the wave of the future, therefore we should drop all VFP development right now.
- I won't be able to find any VFP developers to help me if you go away/die/disappear.

Does anyone have any others they've heard?

To be perfectly honest, I rarely run into any VFP resistance with companies that don't have their own IT staff (smaller businesses). Most of them don't care about the technology, they care whether their business problem is solved (what a novel idea!). This only seems to come up with IT staff who have a bone to pick with VFP because of something they heard five years ago, or some personal agenda to direct business to a friend of theirs or keep some IT function in-house. I guess this "Why VFP" speech needs to mainly handle damage control after people like this have been whispering in the ears of the decision makers. Has anyone been successful in convincing IT staff about VFP? I'm not even sure it's worth the trouble, since they're rarely the people making the ultimate decision. Any thoughts about any of the above rambling? <g>