Hi, Joe: Sorry, but my weekend is pretty full, so I can't answer as thoroughly as I'd like to. String functions in VFP are blazingly fast, but have to be used correctly in ways that aren't always obvious.
CSV with carriage returns inside fields is not CSV, in my not-so-humble opinion. ALL DBMSes have trouble with long text fields. IAC, check out http://fox.wikis.com/wc.dll?Wiki~StringHandling for some clues. MLINE() and _MLINE against your string variable (I know it says it's about memo fields) is what you want, *I think*, but don't have time to check. On Sat, Sep 10, 2016 at 1:32 AM, Joe Yoder <[email protected]> wrote: > I have a routine that processes each character in a file. The file I am > working with is over 2 million characters long. I pull it into a memory > variable with filetostr and then process each character with the substr > command. Apparently substr has problems when dealing with a long string as > the process is painfully slow. > > I suspect that I will be better off using the low level file routines to > read one character at a time but thought maybe someone knows of a way to > speed up the approach I am using now. > > Thanks in advance, > > Joe > > > --- 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/CACW6n4sNMe+yUXR=vhbdru16hzhdeedt9yym+jdogvttuqw...@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.
