(from the first link i could find on G that specified the CVS format)
Not sure how much of an authority this is, but It matches my experience of what's out there.
* *Each record is one line* - Line separator may be LF (0x0A) or
CRLF (0x0D0A), a line seperator may also be embedded in the data
(making a record more than one line but still acceptable).
* *Fields are separated with commas.* - Duh.
* *Leading and trailing whitespace is ignored* - Unless the field is
delimited with double-quotes in that case the whitespace is
preserved.
* *Embedded commas* - Field _must_ be delimited with double-quotes.
* *Embedded double-quotes* - Embedded double-quote characters _must_
be doubled, and the field _must_ be delimited with double-quotes.
* *Embedded line-breaks* - Fields _must_ be surounded by double-quotes.
* *Always Delimiting* - Fields may always be delimited with double
quotes, the delimiters will be parsed and discarded by the reading
applications.Stefan Gonick wrote:
Maybe you can request that they are formatted correctly from your source?
Stefan
At 10:30 AM 4/15/2004, you wrote:
> A properly formatted csv file has double quotes around all fields,
Damn, these files don't have quotes around the numeric value fields.
Wayne
Byte Services Pty Ltd http://www.byteserve.com.au/ [EMAIL PROTECTED] Ph 02 9960 6099 Mob 0409 960 609 Fax 02 9960 6088
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
===================================================== Database WebWorks: Dynamic web sites through database integration http://www.DatabaseWebWorks.com ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
