The application model and data model of .Net is inconsistient with that of VFP. If you forced VFP into that space, you essentially have a language like VB. Yet, VB already exists. Therefore, nothing is gained from having VFP in the .Net space.

It really gets no more complicated than that...


>I would like to understand why VFP will not fit or can’t be justified in the .Net environment. Both you and Rick Strahl have said this. I asked Rick to explain it but he didn’t respond. Your message #408097 was quite good and I’m sure on target. But you really don’t explain why “There basically is zero space for VFP in the .Net environment.”
>Help me out with the reasons why. TIA