>>i have gone i java course lastdays. i couldn't learned java (it confused me) but i learned polymorphism. does vfp support polymorphism if answer yes how?
>
>Poloymorphish to me means that a single interface can have several implementations. Yes, you can do this in VFP.

Is that really "polymorphism", BOb?
In this case I assume (and that may be the problem here < s >) that you mean that within a single method the code can be written to detect specific situations and react as specifically needed for success.

I'd call that simply "programming", not "polymorphism".

When we were first introduced to OOP "polymorphism" was described as a necessary attribute of OOP. I understood that to imply something 'inherent' in OOP. I have trouble connecting my programming for 'an implementation' with an inherent attribute of OOP.
It just feels like there should be something more to it than being WHOLLY based on what I do or don't program.
At this rate it sounds like all that "polymorphism" is is some high-falutin term for doing what I need to do in an application to meet user requirements. A lot like VB6 being "OOP based" to me.

How would VFP not "support" polymorphism?
Would VFP be better able to claim support for polymorphism if it supported different 'signatures' for same method calls?

From someone who has never seen the 'polymorphism' attribute of VFP to date (probably because the definition he uses is lacking something).
>
>BOb