>I know this is kind of strange and unscientific, but I'm most curious.
>
>The question is, how much of your app, written in VFP (excluding foxpro report writer and menu), is OOP architecture?
>
>Mine is about 80 - 85 percent.
I think it is hard to give an exact answer to that one. Depends what you include in "OOP".
In larger projects, I use a framework (Visual Extend), and base all my forms on this framework. That is, on form classes defined in the framework. Sometimes I create additional classes, if I have similar forms.
The largest work I did recently was in Bata-Bolivia, where I worked half-time for the last four years. Most reports were in text-mode, for which I created a class (available in the download section). Therefore, almost all reports were "OOP" as well! Some had inheritance relationships between themselves, apart from being inherited from class cTextReport.
Then, I have a few utilities - most of them defined as functions, not classes.
Some business logic is implemented through triggers (mainly, if changes in one table have to update another table). This is new in VFP, but I don't think it qualifies as OOP. I still find business objects a confusing subject.
As you can see, it is hard to give an exact percentage. But I try to use OOP principles in the larger part of the project.
Regards, Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)