>I think the question about which is better VFP or C# in today's economy is pointless. I searched on DICE over the weekend for VFP jobs in the State of Texas and C# jobs in the State of Texas. There was 1 VFP job and 43 C#. Although I started programing in FoxBase, I have a mortgage to pay and tuition for my kids, today C# is better because I have a better chance of finding a job. I would rather be coding in VFP but I have to look at where I have a better chance of finding a job if/when my current one ends.

Most of the jobs are for beginner or medium programmers - and that's where you can expect the 40:1 ratio between a language du jour and your language of choice. Few years ago it was VB vs VFP (and where's VB today?).

I really don't mind that - I need only one job, and that's in the senior area.

Regardless, the point of my post wasn't exactly "which is better", but rather "what would be an appropriate development benchmark". The initial set of requests to solve was looking, IMO, as VFP-biased, simply because I could solve them all in an hour or two using VFP. Therefore, I was looking for a different class of problems which would be equally easy for ceesharpers, to counterbalance.