Difference: 0LASubrTextParseLine (5 vs. 6)

Revision 62018-05-07 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="APPXRuntimeSubroutineAPI"

.TEXT PARSE LINE

Line: 25 to 25
 <no_of_fields> returns the number of fields that were found in <text_to_parse> (Optional). This must be PASSed with Share "Y" to return a value.

The parsed data will be available in the --- .TEXT PARSE RESULT work field. You do not have to PASS this field. This is a multi occurence work field, each occurence is 512 bytes and there are a maximum of 100 occurrences. If one of the parsed fields is larger than 512 bytes, then --- .TEXT PARSE RESULT will contain 'Data Truncation'. If there are more than 100 fields parsed, then --- .TEXT PARSE RESULT will contain 'Max Occur Exceeded' and only the first 100 fields will be returned.

Added:
>
>

Updates starting in 6.0.1

Starting in Release 6.0.1, this routine has been enhanced:

- All processing has been moved to the APPX engine for faster performance

- The --- PARSED file is returned containing one record for each column. If your application references the --- .TEXT PARSE RESULT field, it will also be populated subject to the restrictions above. The --- PARSED file does not have the same limitations.

- Fields surrounded by quotes will have the quotes removed (unless they are embedded in the the field).

- A backslash acts as an escape character to negate the following special character. For example:

  • C:\\Test will return C:\test
  • "embdded \" quote" will return 'embedded " quote'
 

Comments:

Read what other users have said about this page or add your own comments.

Line: 35 to 48
  -- AlKalter - 2012-06-12
Changed:
<
<
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?
>
>
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

no I am not right. Excel changed the field

Changed:
<
<
-- WimJongejan - 2013-10-15
<--/commentPlugin-->
>
>
-- WimJongejan - 2013-10-15
<--/commentPlugin-->
  -- JeanNeron - 2012-02-10 \ No newline at end of file
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 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