Hi John,

Just to add to what everybody else have said, I have a similar conversion situation that I thought you might be interested in for the sake of a comparison. I have a monolithic app in 2.6 that I designed and implemented over the last two years. The main purpose of this app is reporting. The app works great compared to the FP DOS app I replaced, but it's a monster to maintain (as they say I made my own bed with this sucker).

We want to to convert it to VFP (and VFP only) because:
1. In order to take advantage of all the OOP enhancements to eliminate the maintenance hassles.
2. To salvage our existing code that does the data handling (creating tables, managing tables, processing data into desired format)
3. To salvage all my existing queries and report forms so that they still work with minor environment setting changes
4. To provide a longer application life since I can easily create a VFP app that uses local data, then migrate the data to SQL server, and yet still have that app work with very little changes (local views-remote views)
5. To continue using the fastest database engine and not loose any performance over my current system.

Now we could (and I have tried this) just run our existing app in VFP and fix pieces and parts of it as we go, but we've decided it's easier to run the app as is until we can replace it with a completely new & better way. Yes- you and I can convert 2.6 forms to VFP forms, but my forms got too ugly when I tried it and I care too much about my app to give my users an ugly clunky form. So for me to get this app done in a better way, it requires completely redesigning the app to take advantage of what VFP has to offer and to plan out where we can salvage/copy-paste our existing code into the new app. We also want to make the new app more modularized like you are considering, and again the only way to do that so that the app runs efficiently is to go through the redesigning ordeal.

FWIW, my redesigning and planning ordeal has lasted for 15 months now (but I'm also busy maintaining and supporting the 2.6 app as it continues to grow). And we are looking at kicking off full speed development of the new app at the end of this year. Since we have put so much time into the planning and design of this conversion, we will be able to pull it off easily and with limited resources (crosses her fingers)... or atleast that is what I'm telling myself at this point ;) HTH