>OPEN DATABASE ("c:\mydate.dbc")
>
>No macros.
>
>REPORT FORM ("c:\myreport.frx")
>

Just for clarification:
This could also be written
lcDBC="c:\mydata.dbc"
OPEN DATA (lcDBC)
Is that correct?

I was under the impression that the main reason to get rid of macro substitution would be so VFP could be truly compiled language.
Wouldn't that make named expressions unavailable as well as these would have to be interpreted at run time?

>Now, I know that there are certain options of the REPORT FORM command that oculd legitimately macro substituted, but these fall into the category that I stated before of stuff that could easily be replace by the VFP team with functions that take expressions. For example:
>
>llPreview = .T.
>llPrompt = .F.
>lcScope = "id=1234"
>=RUNREPORT("c:\myreport.frx", llPreview, llPrompt, lcScope)
>

I agree there. That I could live with.