>Bob,
>
>could you give me a brief explanation of early vs late binding with perhaps a "practical example"? Thanks!
>Ken
>

Early binding means that the compiler has already resolved the references to methods and properties at compile time (instead of runtime). Since VB does its compiling as you type each line into the editor (really early binding) it can detect and find references to declared controls, objects and the like. That is also why they can automatically change the variable names to match declarations and detect if your syntax is correct and do true color coding.

VFP does not do this (although I think it can be done). They use the late binding methodology which means method, properties and functions are looked for at runtime and only if they are needed. It is a good idea, since theoretically you can create functions and variables at runtime. It is another reason why we have macro capabilites in VFP and why VB cannot have this.

That is why you can run a VFP program and not get any errors until a function is really needed. In VB you must have all functions even if they never get executed.

I personally prefer the late binding but I wish I had a couple of the VB debugging/development features built in.

Costas