Hiya Joseph.....

>I agree. You need to close a client on VFP? Show him the demo that you've developed. He still wants VB? Move on. Bottom line is this: They know their job; you know your job. If you start from Day 1 with them telling you that they know more about your job (part of that job is knowing what tool is good for the application) than you, it will only get worse. As I pointed-out to the DevDays speaker, VFP handles BUSINESS apps quite well. If you want dancing paper clips, maybe you should pick another language. If you want productive users and quick program enhancements, VFP is a great way to go.

Hear, hear!!! In most corporate LAN environments that I have been exposed to, VFP has no disadvantages. It's fat client but so what? In fact, with frameworks and classes and the rapidity of development and native database calls VFP is *superior* to VB in ROI, RAD, general programmer productivity, etc. I've said it before and I'll say it again: Many line-of-business apps being developed in VB are more suited for VFP....especially 2- (or 3-) tier enterprise applications manipulating large amounts of data.

I just sell the ROI....not the tool.