>Sorry, you'd lose that bet with many. General rule of thumb for estimating time where I used to work was: How long will it take you in VFP? Multiply that by 5. And these were people who knew both VFP and .Net.
>
>"It's all drag and drop.....'til it's not" And most what we needed to do came under the "'til it's not" part.
>
>>
>>
>>Fox's IDE is fast, but I bet you'd be just as productive in .net given the ease of development with prebuilt components (even with a timelag for help). I don't use MSDN help, I google what I'm looking for and zero in on the answer. Much quicker and much less frustration than playing "where do I find what I'm looking for in this MSDN maze".

We have a development shop here with 20+ developers all of whom are skilled in vfp and about half in .net. Our development times in either language are nearly the same. I guess it depends on the skill level of your development team and the architects desigining the system.