>No way! Macro substitution is one of the most useful features in VFP.

Retain PCODE that supports macro.

Build Option:
* Rebuild project
* Application (app)
* Win32 executable / Com Server (exe)
* Single Threaded COM (dll)
* Multi Threaded COM (dLL)

Executable Option:
* Build exe as PCODE / Supports macro subs
* Build exe as Compiled Code / not supporting macro subs

As I have said, PowerBuilder did it. Just my .02 cents worth opinion.

I agree with Eric's perspective. If there is a workaround available or to be provided why not, just to make the product more competitive in the arena. It's a tradeoff issue, are we gaining more than what we give up? If the objective is to make VFP conform with CLR or .NET technology, then I would rather give up macro, anyways there would be a sure workaround.