Hi Pete..

The Implements Clause only comes into play when you are creating COM + Components that will be used in MSMQ (or whatever Windows 2K calls it since MSMQ and MTS were effectively merged).

Whenever you use Implements, you HAVE to implement every member of the interface you are implementing. If you are thinking implements in this context works like VB, you would be incorrect. I thought that was how it was going to work. In VB, if you use implements, whichever class you implement, you automatically get those members as part of you class. In VFP, the class you implement must be in a COM component, and, you have to implement each member manually. In VB, this is an important capability because it helps them get out of the problems of not having inheritance. I don't want to stray too far here because implementing interfaces and inheritance are different things; eventhough the topics often get munged togeter.

Because VB relies on aggregation, the idea that a VB class can implement multiple interfaces is powerful. It would be nice to do this in VFP, in the same way. However, it would be for the purposes of aggregation, not inheritance.

Unless you are going to publish COM + components, Implements will not be of use to you in VFP.

HTH..