Re: csv export...?

From: Date: Fri, 09 Jan 2004 16:40:09 +0000
Subject: Re: csv export...?
References: 1  Groups: php.db 
Request: Send a blank email to php-db+get-32348@lists.php.net to get a copy of this message
Google works!!! just found this, and it works: " On the other side it may be better and easier to create a csv file on the fly. Create a page, say csv-export.php, and link to it using a href="csv-export.php/export.csv". This way the user's browser is tricked that the link points to a CSV file, if it does not honor the content-type it sends (see below). " David T-G <davidtg-php@justpickone.org> 09/01/2004 16:42 To PHP DB list <php-db@lists.php.net> cc Tristan.Pretty@risk.sungard.com Subject Re: [PHP-DB] csv export...? Tristan -- ...and then Tristan.Pretty@risk.sungard.com said... % % On the users computer... OK; that's what I figured. % When my bosses look at the reporting tool I built. % They are gonna hit the export link, and get directed to a page that let's % them save the data as a csv file, for use in excel. Yep. % That's the code I'm working on here today... Look at the header() lines in my reply outside of this subthread. % % ho hum... is it the weekend yet ;-) Not quite, but you're closer :-) HTH & HAND & HNY :-D -- David T-G * There is too much animal courage in (play) davidtg@justpickone.org * society and not sufficient moral courage. (work) davidtgwork@justpickone.org -- Mary Baker Eddy, "Science and Health" http://justpickone.org/davidtg/ Shpx gur Pbzzhavpngvbaf Qrprapl Npg! ********************************************************************* The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. ***********************************************************************

« previous php.db (#32348) next »