>>Well, I didn't mean that you had to by-pass the early exit.< g >
>
>Hehe! I am not worried about a performance hit cycling through a small collection. How many forms could a user have open? If they have more than a dozen or so, they may need therapy.

Split personalities? Each one doing something different?:-)

>>If VFP is doing what I speculated, then, I think, we should view it as a good thing. A PITA for us to have to change? Sure! I'd rather have to make such change if it reduced memory problems, which are very hard to track down. Wouldn't you?
>
>If the FOR EACH is doing garbage collection, then that is definately a good thing! I hope I remember this if/when I convert existing apps to VFP 8. This particular app is new so this is the first FOR EACH in it.

I'm guessing, but I think that's what's up. A couple of years ago I reported a bug with FOR EACH and OLE Automation with Excel (even worked a bit with Garrett on a KB article, which I can't seem to locate now). The solution, as outlined in the KB article was to issue a CLEAR ALL in order to release a dangling reference to Excel in memory. Maybe this is the result of that problem.