Walter,

>Am I correct when I say that anithing that cannot be accomplished by VFP directly may be accomplished by creating a VB (or C#) dll exposing objects and functionality to VFP ? In this way we really don't need to migrate to CLR, then I might qoute JVP (Who would have though I ever would ??): "Use the right tool for the right job"

Yes, or even by calling directly into the .NET framework from VFP. Either of these scenarios involves VFP calling through the COM Interop layer, the performance hit of which is still an unknown.