Tell your CIO this:

"Errors made during the requirements stage account for 40 to 60 percent of of all defects found in a software project (Davis 1993; Leffingwell 1997)"

Extracted from http://www.amazon.com/Software-Requirements-Karl-E-Wiegers/dp/0735618798/ref=sr_1_1?s=books&ie=UTF8&qid=1286992063&sr=1-1 page 4.

Efficiency and productivity problems are not because of the choice of tools, and any attempt by your CIO to assert this is a deflection from the real problems.

Remember, it's ALWAYS the programmers fault.



>I was having a discussion with our CIO who doesn't know anything about Visual FoxPro (9) and has only experience with Classic ASP and VB and he thinks they were great.
>
>He also said that once we get a better programming language (C#) that because it is more efficient all our problems (being behind schedule, etc.) will go away. He also speculated that there were some great 3rd party tools that would make the data access better in C#. Of course, my experience with C# is a couple of web apps that I wrote, using MereMortals .NET and watching videos on LearnDevNow.
>
>I just do not believe that our problems are because of FoxPro.
>
>Most of the coding we do is grab data from flat files provided by the State and push the data into FoxPro tables or SQL Server tables and beat the data up and create PDF reports and spreadsheets. So, we really need and use commands like APPEND FROM SDF or Delim, SCAN FOR, Update, Insert, Replace data in current row, SQL Select etc.
>
>Does anyone know of some magical C# tools that will take the place of those useful FoxPro one-line commands? And I'm not talking about BOs here. No, I doubt it. I think for APPEND FROM (with a FOR) SDF that you would have to write a custom parser for each input in .NET.
>
>Bottom line is that I believe that our efficiency and productivity will go down and we will need more programmers not less.
>
>Yes, I know FoxPro is dead and I'm dying to program in C# only, but what is the truth?