>Is it me or there is no VFP.NET?
>If this is the case, any comments about its inclusion and its role in it.

Getting the name ".NET" seems to require using the CLR (common language runtime). There has been some dicussion in the VFP forum about whether or not it would be good if VFP was to use the CLR instead of its own runtime. The consequences appear to be:

- loss of native data access
- loss of macro expansion
- loss of great string handling capabilities

Personally I would like the best of both worlds. The ability to either compile to VFP runtime (full VFP) or compile to the CLR (VFP subset). VC.NET apparently will be able to do this.