>>>>>>>>>>>>>>>>>>>>
>It's simple; macro expansion treats a . as a terminator, so you can't use field or property references in a mcro-expression. If you read a little aboutr macro-expansion in the docs, it's obvious.
>>>>>>>>>>>>>>>>>>>>
>
>D'ohhhh! You're right. Here I was all this time assuming that it had to do with some subtle difference in the way that VFP treated properties of an object vs. standard variables.
>
>(But that being said, Ed, don't you think your last sentence is a little harsh? I've read more than a little about macro-expansion, and I am fully aware of how the "." terminator works. I missed the obvious answer, assuming something more complicated -- this is not an uncommon reaction to technical issues, even from decent programmers or IS folks. It seems a bit of a leap to assume and state that I have not "read a little about macro-expansion.")

Harsh? Moi? I don't remember breaking out whips, chains or a large trout...

I've developed low tolerance for people who overlook something that should come up and clearly explain why things bite your butt every time you use them. The docs on macro-expansion clearly explain that '.' is a delimiter, and give an example of where this affects macro expansion. I understand the reason that things get overlooked (caffeine deficiency in the early AM, a cow flew by and distracted me, or even it's tough keeping a gallon of knowledge in a shotglass of still functional brainmatter (a frequent problem here)). I -am- totally sick of "WAAAAH! The evil VFP has a bug because it behaves exactly as it's documented to do, not the way I wish it would, and I'm too damned lazy to look to see if it supposed to work this way!" Perhaps I should be more annoyed with Francisco, but there's an overwhelming temptation for me to have simply replied: RTFM because it's there in black and white, and I'm freaking tired of being a substitute for reading the On-Line Help Docs!!!

I'm going back to my cage now... ;-)