>One last comment, .net has been around for several years now. I find it strange that most application I download from the net do not require the .net framework. (Meaning they are not written in .net) So, why do I feel like Microsoft is pushing me to switch to .net. Just allow FoxPro to compile to the .net framework. If they can make many other languages compile to it than why can FoxPro not be ported.
>
>I'm done!
>???????

Net is an infrastructure project tool and most of it will be outsourced across the pond by the less than 10% of those corporations that are not mom and pop. The future is in mom and pop and application design - but the risks are higher. My sense is that most net projects are migrations from MS's last save-the-world-enterprise-tool.

A generalist would work with Java. But the generalist also understands that there is little difference between one object "tool" and "another" (providing the generalist writes "object" solutions).

Besides, with XML and XML messaging we can do anything from anywhere with VFP or delphi or JavaScript - the idea of a "carrier" tool verses an "local" tool is so yesterday. The tool doesn't matter. What matters is how much value the developer delivers with the tool being used.

If it works - don't fix it. If it doesn't work it doesn't mean it will work in NET. Fix the problem. The tool is not the problem. (simple axioms for my simple mind:-)