On Aug 30, 2006, at 10:51 AM, Norman Palardy wrote:
What is the proper method of handling CVS export when there is a
TEXT/BLOB column with illegal characters like Chr(9), Chr(13) and
Chr(10)? Are you suppose to BASE64 encode the data, or are CVS
parser suppose to be smart enough to pick all data between the
quotes (assume all quotes are escaped)?
Since there's no official "standard" there are lots of things you
could do.
Access exports them as is, but few CSV parsers can handle that
(mine can because I needed it to) Excel does this as well.
Since those are, for me, two of the most common sources that I get
CSV fils from I wrote a parser. It works differently than the built
in RB one though because I cannot make it a subclass of any of the
Database objects (RecordSet, DatabaesField, etc) Otherwise I'd make
it work the exact same
Sorry Norman, but I don't really understand your answer. Are you
referring to text data which has been BASE64 encoded, or quote-
escaped string data?
And what is the proper way to escape a quote?
I am mostly concerned with exporting the data from my database into
CVS. I don't really know what software the client would be using to
import the data, although I would think that Excel would be pretty
common.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
