The poster who suggested the "zeroes" could be squares- signifying a
non-printable character, may be on the right track.
However, it occurs to me that you're using quite an unwieldy way of tackling
a simple problem- and that the way you're using is unnecessarily platform
dependent and complicated by the need to handle a return and a linefeed.
I'm not quite sure how your arrays are arranged- as four discreet arrays?
If it's four separate arrays with 10 points and you want one big array, you
can use the "build array" function. If you pop up the right mouse button
menu over this, you see an option to change an input from an element to an
array. If you make a "build array" with four array inputs, what you get out
is one long 1D array with the four sets of data appended one after the
other. If you then want the output as one long column, a useful trick is to
feed your new array into another "build array" node, this time with only a
single "element" input. This promotes the 1D array to a single column 2D
array, that you can then feed through a "transpose 2D array" and then into a
"build spreadsheet string" to generate your output string without having to
do all the search and replace operations. You may or may not need the
"transpose 2D array", depending on how the file turns out- I tend to simply
do things like this without thinking them through and then tweak them to
make them work- which I find quicker than going through all the details in
advance.
wrote in message news:8m9og0$64m$1@nnrp1.deja.com...
> I have a program that arranges 4 arrays which consist of columns of 10
> data points from each iteration of the program. The final program puts
> these sets of 10 pts into one long column. I converted the array into a
> spreadsheet string. I used the match pattern to find and replace the new
> line characters and returns with tabs. Each column has 10 data
> points, then one zero separating them from the next 10 points. I've
> tried the same idea using backspace, form feed, space characters, etc,
> and I still have one row of zeros separating my data points. Does
> anyone have any idea what this character could be or how to fix this? I
> tried all of the characters in the manuals and none will get rid of this
> problem.
>
> Heather
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.