I gotta say - that sure is a WEIRD Problem you are having. I have no
clue as to what else to suggest...
:-(
-K-
On 6/3/2017 12:49 PM, Paul H. Tarver wrote:
That would be the obvious thought, which is why I cleared the data in the
cell and reentered it manually, then I reset all of the formatting to the
defaults and then matched the formatting of this cell to the one above and
below this cell (which I noted were importing fine). Nothing changed it
still imported as '0'.
Paul H. Tarver
Tarver Program Consultants, Inc.
-----Original Message-----
From: Kurt @ VR-FX [mailto:[email protected]]
Sent: Friday, June 02, 2017 11:30 AM
To: [email protected]
Subject: Re: Issues with Excel (Office365) & appendxlsx.prg
Sounds like a format issue specific to THAT cell!?!
-K-
Sent from my iPhone
On Jun 2, 2017, at 11:48 AM, "Paul H. Tarver" <[email protected]> wrote:
I have been using the "appendxlsx.prg" procedure to import data from
Excel (XLS and XLSX) files for a few years now but yesterday I ran
into a weird problem and now I'm wondering if there is a bug in either
Office 365 or Appendxlsx.prg.
A client who has been using one of my programs for a couple years
without any problems contacted me yesterday with an issue related to
data not being imported correctly. The Excel spreadsheet containing
the data is pretty straightforward with less than 100 rows and
probably 20-25 columns. The client creates and maintains the
spreadsheet and then imports the spreadsheet data in my program which
converts it into a file to be imported elsewhere.
All rows have similar data, but in the case of one row, the data was
imported correctly with the exception of one cell. The cell contained
a Case ID which looks like this: "091-293828-012" and that one cell
was imported into my program via the "appendxlsx.prg" procedure as
'0'. Nothing I did to the cell would change the behavior. If I added
characters to the beginning or end of the Case Id, it would still
import as '0'. If I changed the cell contents to '1234567890', it
would import as '0'. The row above this record and the row after this
record as well as all other records in the file imported correctly. But
not this one cell.
Ultimately, saving the Excel file to a CSV format and importing it as
a CSV solved the problem. However, in talking with the client, the
only change that has been made is they switched recently to Office
365. Their problems importing data from the Excel spreadsheet began
shortly after that.
Has anyone seen behavior like this? Is it a problem I need to debug
in the "appendxlsx.prg" program, or is this a bug in Office 365?
Thanks in advance!
Paul H. Tarver
Tarver Program Consultants, Inc.
Email: <mailto:[email protected]> [email protected]
--- StripMime Report -- processed MIME parts --- multipart/alternative
text/plain (text body -- kept) text/html
---
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
