>... continued
>
>4. if you need OO, because your team is too big,

the size of projects VFP is suitable is a matter for a discussion by itself

>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?

I can't say that in advance, that depends on what will MS do
for example if MS will take WORD and will make it into smaller objects
that work together, but can be used seperately as well, this will change
the way i will incorperate WORD into an application,
and IAC VB for applications is already Object based (e.g. excell)
and it is easier to work with