In the time new activeX companents (like treeview) won't be do. What we do in that time?
We won't use VFP with external companents than. So VFP have to in .NET...


>I general do not get involved in these discussion. But, what would we as gain beyond getting to ride on the .NET marketing bandwagon. I like both VFP and .Net. They both have a lot to offer as development tools. But one should use the best tool for the job. I find VFP is great to develop data-centric database application, but loosy to for OS centric drivers or tools. Visual Studio works great in the OS centric world, but more difficult when applied to database application development. Pretty much anything can be done in either language, but which one does the job best? Learn both, and more, and recommend the best language to your client that would best meet their needs and budget.
>
>Just my 2 cents. ( At this rate I be broke by the end of the day.)