Re: [PHP-DB] Re: Convert HTML Table to Tab Delimited .TXT file

2004-05-24 Thread dpgirago
Thanks for responding, Torsten. If I'm understanding your suggestion, then what happens where the data from the dB already has a ; (semi-colon) in it? Wouldn't this corrupt the import into excel? dave My question is whether there might be a more direct way to get the dB data into excel on

Re: [PHP-DB] Re: Convert HTML Table to Tab Delimited .TXT file

2004-05-24 Thread Torsten Roehr
[EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] ... Thanks for responding, Torsten. If I'm understanding your suggestion, then what happens where the data from the dB already has a ; (semi-colon) in it? Wouldn't this corrupt the import into excel? This might cause a problem because

RE: [PHP-DB] Re: Convert HTML Table to Tab Delimited .TXT file

2004-05-24 Thread Daniel . Brunner
really doing But that might be in option... Cheers!! Dan -Original Message- From: roehr [mailto:[EMAIL PROTECTED] Sent: Monday, May 24, 2004 9:47 AM To: php-db Subject: Re: [PHP-DB] Re: Convert HTML Table to Tab Delimited .TXT file [EMAIL PROTECTED] wrote in message news:[EMAIL

Re: [PHP-DB] Re: Convert HTML Table to Tab Delimited .TXT file

2004-05-24 Thread Torsten Roehr
[EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] ... Thanks for responding, Torsten. If I'm understanding your suggestion, then what happens where the data from the dB already has a ; (semi-colon) in it? Wouldn't this corrupt the import into excel? Please take a look at PEAR's

Re: [PHP-DB] Re: Convert HTML Table to Tab Delimited .TXT file

2004-05-24 Thread dpgirago
There definitely are colons, and there is a 'comments' field and semi-colons may appear there. However I think I will include a note in the help file for the admin to avoid using semi-colons in this field. Seems the best solution. And you are right: A .csv is seen as an excel file, so opening

Re: [PHP-DB] Re: Convert HTML Table to Tab Delimited .TXT file

2004-05-24 Thread dpgirago
Thanks, Christian, and all who responded. I think this is almost exactly as it will work. The problem with using some kind of MySQL frontend is that this would involve some knowledge of dB's and SQL (can't be certain of this), and that it would be additional steps. For example, the GUI already