>>
>>I'm happy to say that my daughter and I did a successful 11 hour VFP to .NET/SQL Server conversion stint at a Long Island client this past Tuesday (the day of the deluge)
>>
>>I haven't done one of those marathons in a long time and I slept most of the next day, but it's nice to know that the old bones can still do it.
>
>PMFJI. I am very interested to know more details about your .NET/SQL Server application. If you don't mind my asking these questions:
>1. Did you choose a web .NET application to replace the VFP app? or WinForms?
>2. Does the .NET/SQL Server application have the same look and feel as VFP application? Or you had to change a lot in the UI of the application?
>Thank you in advance for sharing.

Dmitry-
This was really complicated - hence the 11 hours- because we converted the client from one accounting system - DBF to another - SQL and simultaneously brought in a lot of new .NET winform custom apps that use the data from the new accounting system in the customer's sales and factory production systems.

If anyone needed a reason to get off .dbf's looking at what my daughter had to go through converting legacy dbf's that had gone through multiple crashes should convince them.


For back office operations, Winform/SQL Server is my platform of choice.
It's rock solid.
No one wants to say it, but I will - the browser is a primitive platform that's great for certain tasks but in order to even approach what I get with Winform would take budgets at least 10 times the Winform budget and would still be weaker.

One the other hand, we do a lot of simple queries and data collection for clients with the browser using ASP.NET or PHP/Mysql.
Lately I've been leaning toward PHP/MySQL.
It's reminiscent of my days with DBASE on CPM. It looked great at the time, but in retrospect is was pretty primitive stuff.