.NET is huge and it isn't easy to learn. I don't know what approach you took to migrating your VFP app to .NET, but I will say that taking the same architectural approach in .NET that is used in most VFP apps is the wrong way to do it.

In the end, you need to do what's right for you and your customer. If that's VFP, then go for it.


>Every so often a thread starts with the discussion of why MS dumped VFP and if VFP is still a viable platform. So here is another one <g>.
>
>What prompted me to post this message is a bunch of threads currently active that discuss tons of new technologies MS keeps throwing out. My head is spinning. Each one is supposed to be better than the other. Most folk who are really thrilled about these new technologies are a few of really, really bright developers who can "grasp" new tools and work with them. These are handful of people, and I respect them a great deal. There are also those who make living writing books, articles, and teach, and I understand their motivation too. But I know I don't have the brain power and the time to learn the new tools, keep up with the MS changes, and make living at the same time. So I am staying with VFP.
>
>Last year I started converting an VFP 5 application that worked with VFP database to .NET WinForms with SQL Server. Even though I got a great deal of help from a lot of folks (especially Bonnie Berent) it became a nightmare of complexity. And I could see that I won't be able to finish this project in my life time <g>. So I switched to VFP 9, using Cursor Adapter, and SQL Server database. I have to give big thanks to everybody who helped on this project, especially Borislav since he told me (here) years ago how great CA works in VFP with SQL Server. Anyway, I created a small framework based on the CA (basically "universal" BIZ object) that allowed me to make this conversion (from VFP 5 to VFP 9 with SQL Server) at RAD speed. I delivered the project last December and the customer is happy. Funny thing that they are happy that the front end (UI) is almost exactly the same as before. And they don't really care if the front end is VFP, WinForms, or Cloud <g>. They wanted the data to be in SQL Server. And they just trying to get the data in and reports out <g>.
>
>So now I am converting another (very large) application from VFP 9 with VFP 9 SQL Server database, using the same CA BIZ that I already tested on the previous project. The only difference it that this project will need to work with either VFP data or SQL Server data. So even though I use the same classes I have "semaphores" that allow the same app to work with either.
>
>Maybe I am wasting my time since MS no longer supports VFP. But I have never (even once) used MS VFP support. Except buying their updates and patches.
>
>And as much as I don't like the idea of helping MS financially, if I am successful in converting this app to SQL server, they (MS) will benefit. As 100+ customers may decide to buy SQL Server licenses. Although I will always recommend to get free Express version before spending even 1 dollar. And majority of my customers' data is small enough that Express will do the job.
>
>This is probably my only message here that does not end with a question or asking for help <g>