As Ed said, it's not a good idea, but if you really need to do it, you can do EVAL() instead of & in a report.

-Michelle


>Here's my example:
>
>I select the data I want included in the report to follow.
>
>SELECT mytable.&cField FROM mytable ;
> WHERE .... ;
> ORDER BY mytable.&cField ;
> INTO CURSOR rpt
>
>SELECT rpt
>
>I run the report.
>
>REPORT FORM MYREPORT.FRX TO PRINT
>
>In the report designer I want to use rpt.&cField as one of the fieldnames in the report, but it calls it a syntax error. Any work around for this one?
>
>I predesigned the report form using the report designer and supplied fieldnames at that time.
>
>Thanks for your help.