Difference: 0LASubrFileExists (1 vs. 6)

Revision 62014-07-24 - AlKalter

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

.FILE EXISTS

Revision 52014-03-10 - JeanNeron

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

.FILE EXISTS

Line: 6 to 6
 

Usage:

Changed:
<
<
     PASS        <exists?>                 FIELD           SHARE? Y

>
>
     PASS        <exists?>                 FIELD           SHARE? Y

  PASS <pathname> FIELD SHARE? N GOSUB --- .FILE EXISTS * check for errors
Line: 25 to 24
  The subroutine tries to open the file for Read access, and if it cannot, it returns a "N". It cannot distinguish between a file that does not exist and a file it cannot open due to file permissions, both cases will return "N".
Changed:
<
<
You can also use this to test if a directory exists by passing a directory name.
>
>
You can also use this to test if a directory exists by passing a directory name (Unix/Linux only).
 

Comments:

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

Revision 42013-10-04 - AlKalter

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

.FILE EXISTS

Line: 6 to 6
 

Usage:

Changed:
<
<
     PASS        <exists?>                 FIELD           SHARE? Y

>
>
     PASS        <exists?>                 FIELD           SHARE? Y

  PASS <pathname> FIELD SHARE? N GOSUB --- .FILE EXISTS * check for errors

Revision 32013-08-28 - AlKalter

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

.FILE EXISTS

Revision 22012-01-25 - JeanNeron

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

.FILE EXISTS

Line: 14 to 14
 

Description:

Changed:
<
<
This subroutine must be passed two fields. One to return a Y or N if the files exists or not and one defining the pathname to delete.
>
>
This subroutine is called to check if a file exists in the filesystem. Both parameters are required, the subroutine will CANCEL if they are not received.
 
Changed:
<
<
<exists?> identifies the field to return if the file exists or not. Passing this parameter is required.
>
>
<exists?> is the result, indicating if file exists or not (Required). This must be PASSed with Share "Y". Returns Y if the file exists, N if not.
 
Changed:
<
<
<pathname> identifies the field that identifies the pathname to test. Passing this parameter is required.
>
>
<pathname> is pathname to test (Required).
 
Changed:
<
<
This subroutine sets a result value in the corresponding results Token field.
>
>
Notes:

The subroutine tries to open the file for Read access, and if it cannot, it returns a "N". It cannot distinguish between a file that does not exist and a file it cannot open due to file permissions, both cases will return "N".

You can also use this to test if a directory exists by passing a directory name.

 

Comments:

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

Revision 12011-08-12 - PeteBrower

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

.FILE EXISTS

This subroutine is called to check if a file exists in the filesystem.


Usage:

    PASS        <exists?>                 FIELD           SHARE? Y
    PASS        <pathname>                FIELD           SHARE? N
    GOSUB   --- .FILE EXISTS
     *       check for errors
    IF      --- .FILE EXISTS              NE

Description:

This subroutine must be passed two fields. One to return a Y or N if the files exists or not and one defining the pathname to delete.

<exists?> identifies the field to return if the file exists or not. Passing this parameter is required.

<pathname> identifies the field that identifies the pathname to test. Passing this parameter is required.

This subroutine sets a result value in the corresponding results Token field.

Comments:

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


<--/commentPlugin-->

-- PeteBrower - 2011-08-12

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback