Difference: 0LASubrFileSplitFilename (2 vs. 3)

Revision 32012-03-09 - KorryD

Line: 1 to 1

META TOPICPARENT	name="APPXRuntimeSubroutineAPI"

.FILE SPLIT FILENAME

Line: 7 to 7

.FILE SPLIT FILENAME

Usage:

    PASS        <filename_part>           FIELD           SHARE? Y

Changed:

<
<

PASS <etension_part> FIELD SHARE? Y

>
>

PASS <extension_part> FIELD SHARE? Y

PASS <full_filename> FIELD SHARE? N GOSUB --- .FILE SPLIT FILENAME * check for errors

Line: 23 to 23

<full_filename> is the full filename to separate (Required).

Changed:

<
<

The subroutine identifies the <extention_part> by locating all the characters after the last period in <full_filename>. If there are no periods in <full_filename>, then <full_filename> will be returned in <extension_part> and <filename_part> will be empty (the entire name is considered the extension). If <full_filename> contains a leading path, that will also be returned in <filename_part>. See .FILE SPLIT PATHNAME to split the pathname from the base file name.

>
>

The subroutine identifies the <extension_part> by locating all the characters after the last period in <full_filename>. If there are no periods in <full_filename>, then <full_filename> will be returned in <extension_part> and <filename_part> will be empty (the entire name is considered the extension). If <full_filename> contains a leading path, that will also be returned in <filename_part>. See .FILE SPLIT PATHNAME to split the pathname from the base file name.

A 'Data was truncated' error will be returned in .FILE SPLIT FILENAME if the fields you pass are too short to contain either the file name or file extension.

Comments:

View topic | History: r7 < r6 < r5 < r4 | More topic actions...