And the most on the same points. VFP is a dino at of the pre windows area that was quirked into something usable under windows, but the next step is something that is far away from langs better ftting to the windows world. One simply must admit this. Problem is that VFP in itself is very productive :(

>I know of two or three efforts by third parties to write a VFP equivalent in .NET. All failed.
>
>
>>My question was naive, I must admit. It is asked too much to expect modules built with other tools/languages to be aware of all that vfp-apps are aware of. Having admitted that, I now realize it IS important to be aware of this when people (e.g. of Microsoft) claim that new extensions can be built with other tools/languages. In the case of many (vfp) legacy applications that will imply that new extensions will have to act (e.g. upon a database) asif it were a separate executable. So, it will have NO knowledge of the state of variables and settings. And tables will have to be opened as in a private datasession. I think this is all doable, but it will require some (some?) redesign before it can actually be implemented.