>>No way! Macro substitution is one of the most useful features in VFP.
>
>Why? What do you use it for that couldn't easily be replaced? AFAIC, the only legit uses for macro substitution are constructing SQL statements, and the few places where they are necessary because a command doesn't accept a named expression. Except for these, most other uses for macro substitution should be replaced with other methods like EVAL(), or just a refactor.
>
>I would throw away macros altogether if we had the equivalent of the two following imaginary functions:
>
>=RUNSQL("SELECT * FROM MyTable INTO CURSOR Whatever")
>
>=SETENV("EXCLUSIVE", "ON")

Have you ever looked at SBT code? If you removed macro substitution from VFP, SBT will not run and will require a complete rewrite (which, IMO, needs to be done anyway).