Hi Nancy,
As a convention I always use the name reference too as you suggest; but in this case it doesn't work. I'd already tried it. The reason is that m.cFilerpath doesn't persist out of the program - ie it doesn't exist when the user runs the menu. So an & is really essential here.
Regards
Dave

>David,
>
>As a convention, I always use this:
>
>...DO FORM (cFilerPath)
>
>rather than macro expansion. I'm not entirely sure that I'd consider this a bug, because when you macro expand a string with a space, you are obviously losing the...um...connection between the clauses.
>
>Regards
>
>>There's a bug in MSFT's filer.scx (which emulates VFP 3 and FPW "Filer" command)
>>The init event of this form contains...
>> ON SELECTION BAR 21 OF _mtools DO FORM &cFilerPath.
>>Simply amend this to...
>> ON SELECTION BAR 21 OF _mtools DO FORM "&cFilerPath."
>>