There are a lot of advantages to VFP PRG classes. Smaller foot print - cleaner subclassing - the EXE even seems to execute faster. Also gives us a better peek into the bowels of OOP and OOP scripting. Anothe advantage is how intellisense works with PRG classes.

I like the fact that I don't have to drill down thought VCX/SCX property sheets. Cannot corrupt a PRG. PRG are direct access, where as visuall classes are squential. Its a good move.

I did my first all PRG system in last summer. Its so crisp!

For my new projects, PRGs are preferred. Maybe 90% PRG and 10% visual. But, if I'm upgrading or enhancing or building something based on a previous visual model, I still tend to multiselect and paste to the new projects containers.

PRGs are the way to go. There are also some enghancements in VFP 8 that allow us to specify a class in line using WITH to list the property assignments. IOW, we don't need a new line for each propety.


>Hi All,
>
>Two years ago, I've decided to program using only code, I don't include .scx or .vcx nor .mpr files in the final project, I constuct a project with only one object-oriented .prg file (it could be more than one), and .frx and .lbx files for reports.
>
>In this two years of experience, I've found several advantages to this technique. Among them I can list the following:
>
>1. Total flexibility on coding
>2. Easier debugging techniques
>3. The possibility of organize the code using a "treeview & text tool" (see www.treepad.com for example)
>
>I want to know if there are other programmers using this technique, I would like to share advantages and "how's to" with disadvantages.
>
>Also I wold like to receive critique to this technique.
>
>Thanks
>
>Enrique