Hi, Paul.

>I'm seeing this .NET wrapper this same way. Sure, I can write a COM wrapper everytime I want to access something in .NET. But, unless I >really< need it, I probably won't.

No, this is not the case. As presented, the COM wrapper would allow you to instantiate a .NET class, but then you'll need to learn how to use this class anyway, and doing so from VFP would be a lot more difficult than doing it from .NET.

To keep with Michael Asherman metaphor, this would be as if they add some way in which you can write C++ code within VFP and make it run. Sure, you won't need VC++ to to this, but you would need to know C++ anyway, and you'd loss most editor, debugger and environment.

In the end, what Ken propossed is not something that would avoid you having to learn .NET at all. That's why he was unsure about the usefulness of this potential kit.

Hope this helps,