Using a <br> worked. Excellent! Thanks for the tip.

Actually - my team at Porter Novelli are getting really good at doing this stuff themselves. Part of why I’m doing more of this stuff is so that I can keep just far enough ahead of them that they don’t overtake me!

The web really helps, of course. In the old days, someone with limited coding abilities like myself would have to give up when faced by complicated problems (or buy a reference book, which is often the same thing, I find.) These days, Google and the forums help you solve most things; it’s rare that we find that we’re the first person to have discovered a problem; most times we find that someone has trodden the path before and a solution (or solutions) have been provided. Part of the purpose of this blog is to share stuff back into the community that I will have patched together from other people’s work!

Interestingly I’d already come across (and bookmarked) your Top Keywords - Yahoo Pipes post; it helped me solve one of the early problems I’d faced (back when my Pipe was actually working.)

One of the problems I stumbled into (and which I still don’t understand) was the sudden and unexpected failure of Pipes to retrieve my CSV file. Every version I’d used up till then had worked, then - out of nowhere - it stopped working. Cloning the pipe didn’t “reboot”. When I started again from a fresh canvas it fetched the pipes, but couldn’t build the URLs.

I know pipes is a bit beta-y sometimes, but this was just frustrating. Stuff that had worked stopped working. Gah!

Will take a clone of your pipe, if that’s OK, and give you full recognition and links on the new post. Am so pleased. Pipes is a far better tool for sharing with others than the perl script.