>Have you ever figured out how much it costs (tool cost + learning time + developing time + debugging time + ... + ... + ...) to developers using other tools?
>


Fernando,

Tell me, did you not have learning time and developing time and debugging time using VFP for the first time. A new user coming into the software development world has all of these costs no matter what tool he chooses, and I am willing to bet that learning time for .Net compared to VFP for just about any programmer would actually be less (and cheaper) because VFP has only the Universal Thread for support, but .Net has sites such as codeproject.com (> 500,000 members, how many on the UT? - I do think VFP needs a site like codeproject so that new users have all of those code samples to search through).

Now development time, I know that for your requirements VFP is probably all you need, but for most new people coming into the field they will be tasked with developing Web based applications (or PDA application) - now to do both of these in VFP you need to purchase additional software. However everything you need to do PDA and Web based applications is included in .Net, plus based on our experience, doing a web app in asp.net, you could look at reducing your timeframes by at least 30% compared to doing that same web app in WebConnect.

And debugging, all I can say is why does VFP debugger insist on displaying "Source Not Available" all the time, why can't VFP have something like .nets PDB files so that no matter where you run the program from or in what fashion you run it, the debugger could always find the source.


Chris.