Hi Jacob. First of all welcome to the Universal Thread. :-)

Having been in the same situation as you in 1996. I chose to do a conversion of a FP26 app to VFP3. Big mistake for the following reasons:

- I now had an app with the same functionality but was slower. Instead of requiring a 386 or 486 it now required a P75 with 32mb of RAM.
- the application was a nightmare to maintain because of all the code and pageframes that is required to make the old forms and read work in VFP
- my learning curve for VFP was longer than it should have been because I was using VFP in the older 2.6 way

>I find this hard to believe that Visual does not allow for the use of procedural code.

It does, but there is little point to base your entire app on this because you gain little from the new features Visual Foxpro. If all you want is a Windows version of your product then convert to FPW 2.6.

>By the way... I know that OOP etc. is the way to build a new app. I also know that I am not prepared to trash years of work on the alter of OOP. I need an approach that will buy me the time I need to rebuild my code. The look of Windows will do that. BUt I want it to be handled from within VFP..

Good point. There is no need to go completely OOP. Some of your code will still be procedural such as complex sql queries for reports and maybe you have a function library that you find quite good.

For instance one of the first things that developers jump at for OOP is the GUI. Creating form classes, button classes... Later on you may want to move to more complex non-visual classes like a customer class or an invoice class.