In addition to that realize that TEXTMERGE is actually doing a textmerge to disk, so it's pretty slow (well I'm nto sure if it goes to disk, but it is slow). While String concats are not as easy to code, they are a lot faster than TEXTMERGE. Doing TEXTMERGE in any sort of loop is probably not a good idea.
+++ Rick ---
>>As a rule, we strongly prefer the delayed merge strategy-- TEXT TO
, followed by subsequent TEXTMERGE() -- over the use of the TEXTMERGE clause. First, it can avoid the dread "textmerge is recursive" error, which is easy to trigger in a framework or application that does lots of text processing, such as in web applications.
>
>Really? Hmm...I'll have to look at this again. I really wanted to use TEXTMERGE for this stuff (instead of building the strings the "old" way; lcHTML = lcHTML + [String]), but I kept hitting the "recursive" error, and switched back.
>
>Good info...
