>You've brought up a number of the issues I also would like to see addressed in .NET. However, on the databinding, I would like to see VFP take a page from the .NET book... I like being able to bind object properties. It would be super-cool to see Visual FoxPro allow for more than the single ControlSource property or at least be able to define what property the ControlSource effects (other than the Value property for instance). I'm not sure why that has never made it into Visual FoxPro... seems like it is a no-brainer and would make the basecontrols so much more powerful given the datacentric nature of Visual FoxPro. Oh well, I guess it can be done by developers manually in their subclasses somewhat (just not nearly as well as it could be done by the Fox Team in the source).

This type of enhancement would not fit into the way Microsoft plans to enhance Visual FoxPro. The plans for enhancing VFP via Sedna do not involve adding features to the core VFP EXE/DLL (C++ code base) and instead will involve using add-ons to VFP 9.0 extensibility via VFP source code, C++ DLLs/FLLs for SET LIBRARRY TO, and .NET components via COM interop. The plans are to add more and more VFP like functionality to .NET programming while extending VFP 9.0 via interoperabilty and extensibilty (Sedna).