Hi Tamar,

>
No, CustomDocumentProperties is an Office object. The example was meant to show that the loop variable had scope outside the loop.
I know there are some issues with FOR EACH.
>

It is odd that the behaviour should be different in these cases. I don't think I've ever seen the variable stay in scope when dealing with native foxpro collections (including built in ones) but, equally, I looked at some old word automation that I did and it seemed to work everywhere. I wonder if the difference is simply between dealing with COM objects or VFP ones ? Or, if not, what....

Regards,
Viv