>Lawrence,
>
>Take some advice from someone that has some experience with corperate IT politicts. I am a experienced VFP developer and have made the jump to C#. I would advise accepting the project if your boss understands that you will be learning C# as you go and you can not estimate the lenth of time it will take to complete the project. Let him know that you are willing to do this if that is what he wants. That way you are on his side and he will fell confortable with you. Now for the bad news it will take 4 to 5 times longer than you can do it in VFP. He will discover this through the development cycle and your not the bad guy and the company pays you to learn C# is this a great country or what.

That makes a lot of sense but I'm afraid that Lawrence is not living in a "perfect world". Please take no offense Larry in what I'm saying but perhaps Lawrence's position is more delicate than that. If he can get it the way you described than I'd say "Lawrence go for it".

But he previously said that within the company there are other developers that already know C#. So I guess that there could be a possibility for him to lose his job because his boss could decide to let him go and let the C# developers develop that app.

So in the end perhaps it's not only a matter of saying. "What the heck even if VFP is the best solution we'll do like many others and jump on the .net train."

Perhaps VFP is still justifiable in that enterprise. Whatever the tool chosen it should be evaluated very carefully.