>Dear Tom
>
>Thanks.
>I spent the last few years developing in VFP.
>Doing a complete rewrite of a large FoxPro DOS
>application with many modules and a lot of custom
>options and programs for several hundred clients,
>and having been for many years of FoxPro DOS programmer,
>we did things the old way. While creating a visual user interface
>using all the visual classes, much of our code was stored
>programmaticly. We dug into the guts of the classes
>and figured out how to program things the the way we wanted
>it to work.
>Two examples,
>1) Many of our grids were created with a procedure and it allowed
>us to do certain things you would normally not be able to do
>with the grid (e.g. easily copying parts of one grid to a second grid,
>or changing the RecordSource after the grid has been activated)
>2) We created a report procedure that allowed the user to select at
>run time what fields to print, what to group and total.
>It meant a lot of extra work and trial and error.
>
>I am now looking to start some new projects with a much faster
>developement cycle. I think I should go the framework route.
>Can you suggest which framework(s) might good to start with.
>
>Thanks
>Shlomo

Shlomo;

There have been many discussions on this forum about this topic - which framework to use. You can do a search on the UT or on the Wiki. Another approach is the Com Codebook at:

http://www.comcodebook.com/

By all means research before you select a framework. What is good for one person may not be best for another. I use Visual MaxFrame Professional and Visual Fox Express, COM Codebook as well as my own framework, as is required. There are others available that users really like.

Developing your own is not a good idea unless you have a lot of "free time". :) I rather have billable hours and let someone else do the development of an application framework.

Tom