Dawa,

>However, it would be a good idea and very helpful, in my case and many other cases such as
>

>Transform(&lcAlias..FileNumber
>Upper&lcAlias..Name)
>

>for the compiler to issue the programer a warning of some sort.

You might want to look at evaluate() it can be used in your first line above. & macros do have their uses, but I've seen plenty of code posted by people that over use them instead of using other options that work faster.

In the second line, lcAlias could be equal to "(SomeValidTableName" so it would run ok.

The things you are pointing out about "well it should be able to" do make sense when you know what is going to be in those memvars at runtime, but the compiler can't yet read our minds. *s*

>Thank you, David, really appreciated your time and messages.

Me and everyone else in the VFP online community are glad to help.