>if you say cost could only be the difference and they would both take the same time, why different cost?

It is only a possibility. A .NET app could very well cost less than a VFP app. Depends on the developer and his capabilities.

Aside from that, one developer is building an application in a dead-end language that has a dwindling support capability. The other is developing in a mainstream well supported environment. What would you pick?

>
>>Ok - if two guys are bidding on a project and one says they'll do it in .NET and the other says they'll do it in VFP - why possible benifit would there be to it in VFP as opposed to .NET? It simply makes no sense. The only possible reason would perhaps be cost - but with all the various .NET tools and such out there it's not going to take any longer to do it in .NET as opposed to VFP.
>>
>>>I think your comment "I dunno." says it all.
>>>
>>>>I dunno. I've found that even the smaller customers care because they want to be able to find someone to make changes or maintain the application. People are becoming more tech-savy every day, and if a company is paying you to write some software for them generally they're going to want to be using the newest technology so they don't have to have it re-written in 2 years. I'm sure that if you wanted to you could still write a DOS application with Turbo Pascal - but who's gonna want it?
>>>>
>>>>>What is your defintion of "Big Customers"
>>>>>
>>>>>>Big customers care. They want to make sure they have expertise in house to support the app.
>>>>>>
>>>>>>>BINGO! Besides no customer needs to know what the platform is.