Lawrence,
After reading all the replies from the "Anti .NET" people here in the VFP section of the UT you must be getting very discurraged.
I don't think a lot of the people responding to your post realize that sometimes (very often infact) the person with the paycheck is saying that (s)he wants the app converted to .NET. (S)he doesn't care/know if it is a good or a bad choice. Yes I agree that it is your job as the programmer to point out reasons why it shouldn't be done, but sometimes that doesn't matter to the manager.

Changing the backend to SQL is a good thing. If the application structure was written in such a way that the front end has to be rewritten to accomodate the new backend it does make sense to rewrite the front end in .NET (just my $0.02 and I am not saying that .NET is better than VFP).

VFP is data centric yes, but .NET handles data really well too (you don't have to wait until 2007-2008 for .NET to handle data. Version 2.0, being released in less than a month, has some very nice data upgrades)

You should repost your questions in UT's .NET section if you would like fewer pessimistic replies.

Einar

>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?
>
>Lawrence