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 --- _______________________________________________ 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/CABQeDnWd3BawyvK=o5naOb=Dj=8NEPR2xYE4t=s7p1imnpp...@mail.gmail.com ** 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.
