fExeDir (Function)

ONLINE HELP
WINDEV, WEBDEV AND WINDEV MOBILE

Version:

Home | Sign in | English

External file management functions

Application used in Windows Vista (and later)

Path of a system directory

Related examples

See also

Constants for the external files

Functions for handling directories and external files

Handling the external files

Storing files in Android

Summary table: Managing the application directories according to the platform

fCurrentDir (Example)

fCurrentDir

fCurrentDrive (Example)

fDetectRemovableStorage

fDriveReady (Example)

fExtractPath (Example)

fGraphicFilter (Example)

fGraphicFilter

fImageSelect (Example)

fImageSelect

fInsertTextAtBeginning

fIsImage

fListDirectory (Example)

fReadLineRegularExpression

fReportsAndQueriesDir

fSizeUncompressed (Example)

fSizeUncompressed

fSplit

fStopCompress (Example)

fUncompress (Example)

This content has been translated automatically. Click here to view the French version.

SOAP server
Application used in Windows Vista (and later)
Path of a system directory

WINDEV

WEBDEV

WINDEV Mobile

Others

See also

fExeDir (Function)

In french: fRepExe

Returns the directory from which the execution is started.

Returns the runtime directory of the project. This directory must be accessible in read/write mode. In most cases, it contains the data files and the other files handled by the WEBDEV site.

Caution: fExeDir is used to find out the runtime directory while fCurrentDir is used to find out the current directory.

Versions 15 and later

This function is now available for Android applications.

New in version 15

This function is now available for Android applications.

Versions 16 and later

This function is now available for Windows Phone applications.

New in version 16

This function is now available for Windows Phone applications.

Versions 17 and later

This function is now available for iPhone/iPad applications.

New in version 17

This function is now available for iPhone/iPad applications.

Versions 18 and later

This function is now available in Android widget mode.

This function is now available in Windows Store apps mode.

New in version 18

This function is now available in Android widget mode.

This function is now available in Windows Store apps mode.

This function is now available in Android widget mode.

This function is now available in Windows Store apps mode.

Versions 21 and later

This function is now available in Universal Windows 10 App mode.

New in version 21

This function is now available in Universal Windows 10 App mode.

Example

// Répertoire de lancement
Info("Cette application a été lancée depuis " + fExeDir())

Syntax

<Result> = fExeDir()

<Result>: Character string

Directory from which the executable is run. This path does not end with the "\" character.
In test mode (GO from WINDEV), corresponds to:
the generation directory given in the description of the current project configuration.
the EXE subdirectory of the project directory.
At run time, corresponds to the directory containing the current executable.
Runtime directory of the project. In test mode and in deployment (GO from WEBDEV), corresponds to the EXE sub-directory of the project directory.
Versions 15 and later
Setup directory of the application (in the internal storage area).
New in version 15
Setup directory of the application (in the internal storage area).
Setup directory of the application (in the internal storage area).
Versions 16 and later
Data directory of the application.
New in version 16
Data directory of the application.
Data directory of the application.
Versions 17 and later
Root directory of application (accessible in read-only).
New in version 17
Root directory of application (accessible in read-only).
Root directory of application (accessible in read-only).

Remarks

SOAP server

The fExeDir function used on a SOAP server returns the path of the directory containing the library of the running SOAP server.

Application used in Windows Vista (and later)

In Windows Vista (and later), the UAC mechanism implies some development constraints.

Therefore, the files used by the application (data files or INI files for example) should be stored in the specific directories of the application (and not in the directory of the executable). These directories are returned by fDataDirCommon, fDataDirUser, fGlobalDirCommon and fGlobalDirUser.

Path of a system directory

To find out the path of a system directory, use SysDir.

Related Examples:

Unit examples (WINDEV): Handling text files

[ + ] Handling "text" files with WINDEV:
- Create a text file
- Write into a text file
- Read in a text file

Unit examples (WEBDEV): Handling text files

[ + ] This example explains how to handle "non HFSQL" files with WEBDEV and it allows you to:
- Create a text file
- Write into a text file
- Read in a text file

Unit examples (WINDEV Mobile): Handling text files

[ + ] Handling external "text" files:
- Create a text file
- Write into a text file
- Read in a text file

Component: wd270vm.dll