>Jill,
>
>Yeah, I started out 11 years ago with FoxBase, then FoxBase +, FoxPro, FoxPro for Windows, and then I stayed at 2.6 for years
>because I was happy and comfortable and could do what I wanted. However, with the newer versions of Windows my clients started
>experiencing incompatibilities forcing me to leap to VFP 6.0. Man, I had a HORRIBLE time making that transition. That was 9 months
>ago. I now know enough to get things done, but a lot of my methods could use refinement. That's where I'm learning so much
>from the Universal Thread. People like you who are willing to take time and offer valuable suggestions have made the process
>soooooo much easier. I got into a local users group (GRAFUG) and have been amazed at how much power and flexibility is
>available in VFP.
>
>Anyway, I thank you again for your time and suggestions.
>
Fred;

One thing I learned about Visual FoxPro since I had a copy of VFP 3.0 Beta, was you should create your own framework. After three attempts I had a reasonable framework that was very functional. After going through CodeBook, Visual FoxExpress, and Visual MaxFrame Professional, I decided to use your own framework without being paid to develop it is folly. By letting a team of experts develop your framework you can get on with doing what your clients need - application development. Combine a good framework with VFP and you have a combination that cannot be beat.

Tom