>ISTR getting burned once by TEXTMERGE - I was maintaining some existing code and had to wrap one in other code. For readability I indented the TEXTMERGE which caused it to fail, I think because tabs were introduced. Any code which fails when indented by tabs is too fragile for me so I've never used it since. I think in that case I moved the TEXTMERGE to a separate routine/method with no wrapping/indentation and commented it to leave it that way.
>
>I find when I'm building strings I like to be able to see the individual components, mainly for debugging. Doing that conventionally with assignments works well for me. How easy is it to see the contents of a TEXTMERGE in the debugger?

I use it all the time with indentations and multiple lines, mainly for my SQL statements, and tabs are of no issue if you use the appropriate pretext options, one of which is to remove tabs