David,

I suggest that you split your resources (e.g. time) as follows:

[1] Get a good commercial framework and learn how to use it with your current project(s). Don't worry about OOP Design Patterns or anything else that will distract from learning how to use the framework with your project.

[2] DIG DEEP into VFP, it's object model, class design, n-tier design, etc. Get all the books/articles/white papers and read them all. You will begin to appreciate the power of VFP and see how it can be applied (and how it is already being utilized by the framework you are using for your project) to create solutions. This is what you do at home with your free time at night and during the weekends and throughout the wee hours of the morning. Don't plan on getting much sleep from here on out.

And don't forget SQL Server.

And if you have any extra time, you can give yourself the Ivar Jacobson, Grady Booch headaches.

The bottom line is to get up-to-speed and productive with VFP as fast as possible. This can be a very long process, so don't bog yourself down with theory - learn by doing.


>Hi Jeff:
>
>I concur with you -- and the others who suggest I move to the OOP paradigm.
>In fact, I'm on the path now. Sharrie was just hoping we could get something out the door to support us whilst we complete a truly OOP project.
>
>Now I'm trying to think in the following terms, rather than procedural:
>
> OOP
> n-tier
> GUI
> PEMs
> composition in favor of inheritance
> Patterns: including Mediator, Interpreter, Iterator, Visitor, Chain of Responsibility, and Bridge.
>
>Do you think I can get all this down in a week? j/k
>
>David Powell
>WagnerSys@aol.com