Franki, Why not solve this issue on the template level? Just create a separate template for CSV output similar to the original one that produces query result in HTML. # Automatically generated CSV output <TMPL_LOOP rows> <TMPL_LOOP cols>"<TMPL_VAR field>"; </TMPL_LOOP> </TMPL_LOOP> This way you can keep all your existing processing logic. All you need is to branch based on a csv flag and use this alternate template. I haven't tried this in real life, just an idea. You probably need to check extra newlines and refine this template for your specific environment. Also this template does not prevent special characters like newlines, quotes from breaking CSV syntax. Peter | mailto:suppressed | http://www.VRtheworld.com --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/suppressed/ To unsubscribe, e-mail: suppressed For additional commands, e-mail: suppressed
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.