A couple of SWAGgy comments, may or may not be useful:

- Did you have that code block indented? You may have noticed that causes the output to be indented as well. I remember first working with it years ago and running into some weird things when it's indented, my personal rule is to never indent it

- Might you have had any weird DEFINEs set?

>Dragan --
>
>No, that couldn't be it, as I was no even aware that there was a feature 'Set TextMerge'.
>
>In any case, while I didn't understand what caused the error, I also don't understand what I did that made it go away.
>
>
>
>>>Koen --
>>>
>>>OK, but what could that be? AND -- if the code fails, because it is recursive (note that it doesn't even use TextMerge!), why when I resume execution does it not fail.
>>
>>Could it be that you had a Set Textmerge On already? Fox actually has only one textmerge handle (_text variable) for the old output-to-file merge mode; the new text-to-variable and textmerge() can mess with it if it's still open while they execute.