Unfortunately, it's easier said than done. One notorious example is the Palm
Desktop software. Since the very first version they have insisted on
exporting the returns within fields like "address." I first wrote them about
this in 1996 but they never did anything about it. The ASCII 11 protocol
that FileMaker uses to represent returns within fields is not universally
employed.
However, bobchabot is not stuck to do it by hand every time. He can import
the entire text file into a single field. Then he can use an
algorithm/script to identify the returns which should be kept, vs. the ones
which should be removed/converted. That field can then be exported and
re-imported as records.
The exact code for this would depend on the contents/appearance of the
actual import file. Fortunately there are usually some patterns/markers in
such files which enable someone to perform this cleanup automatically.
Bill
"Matt Wills" <I'm (AT) Witz (DOT) end> wrote
Quote:
So, yes, you'll have to clean out the stray CRs before FM can do what you
want it to do.
Better still, see what you can do about getting cleaner source.
Whatever is generating your CSV is not doing such a great job of it if
there are stray CRs all over the place.
Matt |