Difference: 0LASubrTextParseLine (2 vs. 3)
Revision 32013-10-14 - WimJongejan
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
.TEXT PARSE LINE | ||||||||
| Line: 36 to 36 | ||||||||
| One work-around would be to read through the string beforehand, keep track of when you're within quotes and when you're not, and change the actual delimiters from commas to tabs, since tabs are rarely found within field content. Of course, you could use some other character as well, but I found that tabs did the trick. -- AlKalter - 2012-06-12 | ||||||||
| Added: | ||||||||
| > > | i have an input file where date fields are displayed as for example 4-3-2013 To my astonishment the field --- .TEXT PARSE RESULT is now filled as 2013-03-04. I have looked a few times but it seems the subr. .TEXT PARSE LINE does that too. Am I right? -- WimJongejan - 2013-10-14 | |||||||
| -- JeanNeron - 2012-02-10 \ No newline at end of file | ||||||||
View topic | History: r11 < r10 < r9 < r8 | More topic actions...
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding TWiki? Send feedback