>>There are also a lot of things that cannot be done with .NET and a lot of markets where .NET is unsuitable.
>
>I have not a large experience in .NET, but since now the only thing I have found that cannot be done in .NET is macro substitution.
>I think the others *can* be done. In a different way, spending different amuont of time, but they can be done.
>If you refer to the "data management", have you looked this?
>

Macro substition is an implimentation detail, that isn't necessarily necessary in other languages. For example, it is useful in VFP for constructing portions of a SQL SELECT statement. In .NET, the entire select statement is put into a string, so it is not relevant.

That being said, the ability of VFP to run a .prg file on the fly, even without the development environment, does give a lot of flexibility. A system could be designed so that certain hooks could be modified by the end users of a product, by allowing them to modify certain .prg files. That opens all sorts of issues regarding security and ways of accidently breaking the system.

At runtime, a VFP program can create its own code, on the fly, and run it. That's cool.