Help / WLanguage / WLanguage functions / Standard functions / External file functions
  • SOAP server
  • Application used in Windows Vista (and later)
  • Path of a system directory
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WindowsLinuxPHPWEBDEV - Browser code
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac CatalystUniversal Windows 10 App
Stored procedures
Returns the directory from which the execution is started.
WEBDEV - Server code 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.
// Runtime directory
Info("This application is started from " + fExeDir())
<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 runtime, corresponds to the directory containing the current executable.
WEBDEV - Server code Runtime directory of the project. In test mode and in deployment (GO from WEBDEV), corresponds to the EXE subdirectory of the project directory.
AndroidAndroid Widget Installation directory of the application (in the internal storage area).
Universal Windows 10 App Data directory of the application.
iPhone/iPadIOS WidgetMac Catalyst Root directory of application (accessible in read-only).
WINDEVWEBDEV - Server codeReports and QueriesAjax

SOAP server

When fExeDir is used on a SOAP server, it returns the path of the directory containing the library of the SOAP server being run.
WINDEVUser code (UMC)

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:
Handling text files 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
Handling text files 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
Handling text files 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: wd290vm.dll
Minimum version required
  • Version 9
This page is also available for…
exemplo pegar pasta local
Esse Video vai estrear as 10:00 do dia 11/06/2021
sNome_pasta is string=fExeDir()+"\copia\"
sArquivos_retorno is string=fListFile(sNome_pasta+"*.*") // Vamos ver quais arquivos estao nesse diretorio
LIST_arquivos.DeleteAll() // Cria o list box, -: é opcional

sNome_arquivo_zip is string="arquivo"

FOR EACH STRING sArquivo_individual OF sArquivos_retorno SEPARATED BY CR
LIST_arquivos.Add(sArquivo_individual) // adiciona no list box para ver os arquivos é opciona
IF CBOX_criar_Executavel=True THEN
NOME_ARQUIVO_eXE is string=fExeDir()+"\"+sNome_arquivo_zip+".exe"
06 Jun. 2021

Last update: 06/22/2023

Send a report | Local help