Most of us do not have the luxury of throwing everything we know away and starting over, which is what jumping directly into OOP requires.
Our approach was to start slowly. If an application was well designed in the 2.6 world, we moved it up to VFP by simply converting those things that absolulely needed to be converted. There was more than enough to learn about building the new forms and menus without also having to learn a totally new way of thinking about system design.
We are still maintaining some of those old applications for clients who could care less about how we get their work done, (which translates into the fact that they are not willing to pay for a complete redesign.) Because the applications are in the VFP world however, we are able to introduce the new technology one module at a time. Usually when a client gets a taste of the new and better things you can do, they will want more, and that will fund your learning.
As long as you keep an open mind, and look for opportunities to use the new tools and capabilities, you will be able to evolve into the new world. To state a silly, but very meaningful cliche, "... you can't move a mountain all at once, you must begin with one shovel at a time."
Ev