Hi!

Michel, this help article is not what you thought.
You're talking about early/late binding at client side, when you use VFP code to bind to events of some COM object.
That article describes opposite - from the COM object side: describes that VFP supports both approaches (early and late binding), and gives an example of how you can use *VFP* COM object inside of teh VB client - using both early and late binding.

This is from my MSDN:
>>>>
Visual FoxPro COM servers support both early (vtable) binding and the existing late binding (IDispatch) interface (together known as dual-interface support). Binding describes how clients access properties and methods of a server. Early binding provides performance benefits for Automation controllers that support early binding such as Visual Basic and the Microsoft Transaction Server. While Visual FoxPro servers support both interfaces, the one used is determined by the client.
>>>>

To read more about late binding in VFP, take a look to the help on EventHandler( ) function.

So seems that article correct, though it is good idea to send feedback to MS to improve this article so users will be not confused about what is described there.

HTH.

>>>When I go in the Visual FoxPro help and access "binding / early vs late", I am given a Visual Basic example. Where is the Visual FoxPro example? Am I missing something?
>>
>>Same here. As I understand it, the help is talking about VFP COM Servers and since VFP does not have early binding, VB code is just an appropriate example because it does support early and late binding.
>
>I still think that part of the help was not completed. It should deal with VFP or at least explain more in regards to it.