×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 1/16/2013 12:05 PM, John Yeung wrote:
The Excel *parser*, whose job it is to interpret data loaded from CSV,
is the thing that really drives everyone nuts. This has nothing to do
with the Excel file format, though.
I completely agree with your analysis. I think we're looking at the
same thing from different perspectives. I often receive a spreadsheet
where a single column is inconsistent between rows. I can imagine the
original sheet was imported from a CSV and the user inserted rows in the
middle, and it's not Excel's fault that the CSV parser made the ZIP code
text and the newly inserted rows have the ZIP code numeric - that's how
Excel is supposed to work.
Excel doesn't care if row 10 has ZIP=text and row 11 has ZIP=numeric but
we DB2 people sure do. A utility like XLS2TABLE will necessarily try to
convert a given cell according to the type Excel reports, but custom
code can cast that to the result you want.
--buck
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
