One problem with using .CSV files and Excel is long digit strings (such as account numbers). I've not found a way in a .CSV file to get them to appear correctly in a spreadsheet. I'm always forced to add a prefix to turn it into a string, and the sheet shows the annoying prefix.
So unless I'm missing something, there are a few cases (in addition to pretty formatting) where creating a spreadsheet is preferable to a .CSV file.
Example:
1234567890123456,"1234567890123456","'1234567890123456",'1234567890123
+456
1234567890123456,"1234567890123456","'1234567890123456",'1234567890123
+456
1234567890123456,"1234567890123456","'1234567890123456",'1234567890123
+456
1234567890123456,"1234567890123456","'1234567890123456",'1234567890123
+456
1234567890123456,"1234567890123456","'1234567890123456",'1234567890123
+456
1234567890123456,"1234567890123456","'1234567890123456",'1234567890123
+456
1234567890123456,"1234567890123456","'1234567890123456",'1234567890123
+456
1234567890123456,"1234567890123456","'1234567890123456",'1234567890123
+456
Someone ...
anyone ... please prove me wrong!
...roboticus
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.