When one imports a .CSV file with carriage returns embedded in a field that is delimited by quotation marks, Foxpro ignores the quotation marks and assumes any carriage returns it finds indicate the end of a record. The file I am working with ends up with several hundred extra (garbled) records because of this fact.
When the file is opened by Excel the problem does not occur. My question is if someone is aware of a solution to this problem. In this particular case, I think I can do a workaround by simply eliminating the problem field . Sooner or later I will probably get into a situation where I end up writing my own import but it hasn't happened yet.
Thanks in advance for any solutions or ideas,
Joe
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---
You can always write your own routine to do the job instead of relying on APPEND FROM! I sometimes needed to do that...
On Sat, Sep 10, 2016 at 2:25 PM, Joe Yoder joe@wheypower.com wrote:
When one imports a .CSV file with carriage returns embedded in a field that is delimited by quotation marks, Foxpro ignores the quotation marks and assumes any carriage returns it finds indicate the end of a record. The file I am working with ends up with several hundred extra (garbled) records because of this fact.
On Sat, 10 Sep 2016, at 07:25 AM, Joe Yoder wrote:
When one imports a .CSV file with carriage returns embedded in a field that is delimited by quotation marks,
You are going to have trouble with this no matter what. You will have to roll your own import.
-
Alan Bourke -
Joe Yoder -
Man-wai Chang