>Don't use macros unless absolutely necessary. If lc_printsel contains blanks, your code will break. Use name expressions instead. In this case you should replace &lc_printersel with (lc_printersel).
>
>>An application deployed at customer's site throws an "Invalid Path or Filename" error when attempting to preview or print a report. Except that report was compiled into the EXE. Other customers are not reporting the same error. The line of code is:
>>
>>REPORT FORM (lc_reportname) to printer &lc_printersel. preview noconsole ; && GreyHawk - 20080701 - add printer selection for preview
>> WINDOW (Lo_RepForm.NAME)
>>
>>Where lc_printersel contains 'prompt' (or empty, depending on customer settings).
>>
>>Chris.

I inherited the application and correcting the (ab)use of macros is on my hit list. I'll look into the space thing though.