Kayda,
You best bet would be to convince the file source party you and they have no
choice, but a new clear delimiter protocol. The actual data cannot contain
delimiters. My favorite delimiters are from char(128 - 255) range. If you
positively have no choice, in theory the parsing could be done by loading
everything into a temp table with just two columns in it one being data
receptacle and the other being identity to keep the row sequence handy.
During load break rows with proposed row delimiter than parse data to adjust
the each row content, and than parse rows into real columns separating them
by the | sign. That is to me too much trouble.
Ilya
"kayda" <tabladude (AT) gmail (DOT) com> wrote
Quote:
I've been given a series of text files where all the fields are
delimted by a vertical bar, but each row takes up two rows in the text
file. So if I use any delimter like CR or LF etc., it treats each row
like two rows, since each row just finishes with a vertical bar and
then a return.
Is there any way to deal with this? I could send an example file if
required?
Thanks,
Kayda |