... continued

4. if you need OO, because your team is too big, because the scope of your project, or because of the sheer complexity, do not use VFP. VFP is great by definition for projects of which the semantics can be remembered without extensive documentation. Most of the benefits of OO stem from the fact that the semantics of the system can be embedded into the code, easing project management and inter-team communication, not to forget the sacro saint reusability factor. But all those considerations are rather far away from the daily concerns of the modal VFP developer.

5. All this does not mean that the OO features in VFP are not useful, or that OO is not an interesting development, but that OO in VFP is of minor importance and that it is as this thread suggests no more than a nice syntaxic enhancement. If tomorrow M$ issues Word, or Excell with possibility to define classes and instantiate objects, would you not agree that this does not necessarily mean you have to rethink your approach to macro writing?

to be continued