Don

I took the approach I can do this in VFP, how do I do the samething if C#. If I couldn't I explored
> reasonable alternatives. In between I asked a lot of questions.

This IMO is a bad idea, .Net is a completely different bag to VFP, that's why I question whether 3 months is enough, the learning curve is HUGE, it's not trivial to pick up the language AND the framework.

You would have to design your apps from the ground-up using an OO approach, but again, if your confidence in OO is not 100% you will have shortfalls there as well.

Learning and becoming proficient in c#/.net is not a trivial matter, you also have to get up to scratch with OO concepts as well, but it's only when you get to this stage that you appreciate some of the benifits.

We took the approach of creating an in-house object-driven framework and it's starting to pay off now, we can knock up a small application in a matter of hours containing very rich functionality, it can be web-based and windows-based and still use the common object-model, it's easy to maintain, there's minimal code to write (no SQL, no connections etc.) and you never get silly bugs because it's built on a solid framework - but then this all takes time and you need to take that object-driven approach, what you need to question is whether you want stability or minimal developer-effort. I'm not saying your VFP apps are full of bugs but I would argue that maintainability of your app is easier with C# than it is due to VFP, although again I will say that this is mainly true if you take an OO approach, all swings and roundabouts really.

Kev