For each...next within for each...next

[CADfunk MC]

A program I made up has a very long for each statement. Somewhere within the for each..next procedure, a block is made. But sometimes the block is made twice (on a crosspoint in the drawing).
I want to avoid this, but the only way I can think of, is by making a "for each" statement within the first" for each" statement, that skips to the "next" statement of the first one if the blockname already exists. But that seems clumsy, and I'm not even sure if it's possible. Anybody have a good way to handle this situation?

[Ed Jobe]

Clumsy is kind of relative. You need a set of logic to define the conditions under which an event happens. You could try to define all the conditions up front, but then you have to apply that logic to every descision. Its better to keep the logic as simple as possible and apply it only where its needed.

[B_Roche]

you also have to be careful when looping thru collections ... the collection can update on you as you add/delete entities, because by doing so, you are changing the collection.

Loop thru the collection once, grab the handle/ObjectIDs that interest you, then go back in a separate loop and do your modifications.