Hi Paul,
thank you for your time, your knowledge is valuable.

I agree with you,
of course the above is more painful than processing it, inside access, even if the "ecological niche" of the process must reside inside word, as this processing belongs to the word document.

The problem described, above is part of a repeating process via which a repeating structure (building block) is inserted in the doc as a "variable rows" repeating scenario that derives from a one-to-many relationship in ms access.

1. The "one-to-many" query is extracted from ms access and the selection point goto a word bookmark.
2. Invisible custom fields are inserted ({set ...}).
3. A building block is inserted "many" times transforming itself according to internal custom fields {if ...}
4. The building block is selected and custom fields are unlinked inside it, and, loop...

The same custom fields can be reinserted and reused according to the "next row" logic.

The scenario is already complicated without the proposed conditions, so, I will process it in MS access during the query

Best Regards

Theodore Panos