Mr. B,

I met you at Devcon. Good to here from you.

My point (to all), is that I believe "Base" means "having the lowest level in the hierarchy", and that that position can only be held by a single entity. From what I've been able to gather we will end up having multiple "lowest level" forms, labels, combo boxes... so if we decide to change the font on all labels or the background of all forms, it will need to be done in multiple places. To my mind, this removes some of the advantage of heredity.

We could all write our own "Seek" or "Transform" utilities that supplant the native FP commands until each shop has it's own version of the language, but we don't. In practice we treat the commands as though they were sacred.

The real question is: Should we treat the FFC as a permanent extension of the language, one that we will all use as our own Application Framework?

My guess is no.

>>Does anyone believe that the Foxpro Foundation Class libraries will be the new standard? It seems to have so many holes and inconsistencies in it, like not using views, looking up by Record Number!?!
>>
>I don't think the FFC will become a "standard" outside of the fact that it does exactly what it is designed to do, make it easier for new users to get into VFP.
>
>We will still have our own classes for our own purposes, but the FFC classes may be helpful in places.