This is sort of a half-way solution, but so far it's the only one I have found.

I tried Sesame's QA Translate and was very surprised at how simple it is. The only caution is that before the translation you MUST remove ALL double quotes or the CSV records will get screwed up.  That is a CSV "thing", not a QA or Sesame "thing".

This can be done using a Mass Update for each text box field.  (I am assuming short fields such as School won't have double quotes.)

In each field that needs to be sanitized use this as the update spec: #1=@Replace(#1,@chr(34),@chr(96))

The number after the number sign must be different for each field.  That will replace all double-quote characters with a back-apostrophe (the one under the tilde on a U.S. keyboard), which is normally unused.  If you really want to keep the double-quotes, you can run the same update in reverse in Sesame. It probably would be better, however, to replace the back-apostrophes with two regular apostrophes.

Then translate to Sesame.  Sesame preserves the blank lines.  Then export the records in CSV format from Sesame.  The difference is that QA simply removes the control characters that create blank lines but Sesame replaces them with \n.  Once the Sesame CSV records are imported into some other program (e.g., Excel), the \n can be converted to whatever that program uses as EOL.

Now that I have worked a bit with Sesame, I can see that it is MUCH easier than other database programs, such as FoxPro (that I am familiar with) and Access (which I flat-out gave up on after spending $163 on a bunch of manuals trying to figure out how to do some fairly simple programming.)  It looks, however, like I will only be updating parts of our QA application, which will result in bi-directional transfers between parts of the QA application that will be kept and Sesame replacements for others.  I don't know whether I will have to transfer large text fields back to QA but if so I don't know yet whether there is a way to @Replace the \n once the data is back in QA.