>What I don't get about this is, if they can call a .NET form like an ActiveX control, why not an AciveX type container for .NET controls?
>
>I have a number of places I can think of where I could see using a control written in .NET, but only a very few where a whole .NET form would be usefull. I would do more .NET coding if I could create usable VFP controls the way I do now with c++.

That is a good idea. I'd certainly could use something like that in some situations. At this point it is my understanding that Sedna is still very much an open book. The feature set is far from complete. In fact it is just starting so it would be a good idea for you to document and request your idea. At this point, who knows what they'll decide what's feasible or not.