>I have a VFP application that my division manager want converted to C#.NET. I am not familiar with C#.NET enough to know if it is indeed superior to VFP or if my division manager just wants something done in C#.NET. Can someone enlighten me?

If you don't know C# well enough, than it is definitely inferior, at least, if you are going to do the programming. It may become equal to VFP eventually, but learning any new programming language takes several months, at least, before you start to be productive.

You also mentioned about "if the back-end is not VFP, why use VFP at all" - well, the same argument can be made for C#, Delphi, or whatever. If the backend is not C#, why use C# at all? Of course, you can't use C# as a backend, but the point is, VFP is not ONLY a database backend. It can also be used to design the front-end. The question is not so much "why use VFP at all", but rather "why not", especially if you already have your application in VFP, and a programmer, or programmers, with VFP experience.