On Wed, Sep 10, 2008 at 01:45:46PM +0800, Brett Payne-Rhodes wrote: > > I don't think list processing is clever enough to say "Ignore delimiters that > are inside double quotes" so it treats the comma inside your 'third' element > as a valid delimiter. > > You might have to run a clever bit of regex to replace said commas before the > list processing and once you have the element then simply restore the commas. > > Someone cleverer than me will need to provide the regex though... :)
In the dim distant past I did list management for a living. A significant amount of our time was taken up with working around these sorts of issues. My suggestion would be that if at all possible you get the originating data in a more modern format. XML is good, but almost anything beats csv. Or if you can't change formats, see if you can get the delimiter changed to a non-printable charcter such as TAB. If you can't finesse the source data, you're going to end up with The Regex From Hell (That Gets Tweaked Every Run) or lots of brute-force loops-within-loops code (that also gets tweaked every time). Paul Haddon Technical Services Manager Formstar Print Technologies --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~----------~----~----~----~------~----~------~--~---
