AFAIK, Powerbuilder have the option to compile into PCODE or Machine Code at least in Version 5. Why not in VFP if the issue is just to maintain Macro Substitution support? Anyways, since we already got INTELISENSE, CLR shall follow if it is that necessary. .NET technology is just about to begin...
>Dear all,
>
>Now that the .Net dust has settled a bit, we know that VFP is not going to be able to run on top of CLR. I was thinking that maybe that MS could just strip out support for macro subsitution from VFP. Since the release of Visual .Net is still at lease 6 months out some work can still be done. Other languages like cobol, Effiel and others are going to support CLR why not VFP? I can live without Macro subsitution if that is in the way of CLR support. Does anyone support my idea? Thanks.
>
>Regards,
>Kueh.
JESS S. BANAGA
Project Leader - SDD division
...shifting from VFP to C#.Net
CHARISMA simply means: "Be more concerned about making others feel good about themselves than you are in making them feel good about you."
