Skip to content

Development File Names & Extensions

This topic covers the file names and file name extensions for DataFlex programming-related files. See Embedded Database File Names & Extensions for information regarding file names and extensions for the embedded (DataFlex) database.

The following are the standard file names and extensions used by the DataFlex development tools.

In some cases, you are not required to use the standard file names and extensions. However, we highly recommend that you do, because the Studio and other development tools are geared towards the standard file names and extensions. In addition, using standard file names and extensions makes code more maintainable since other DataFlex developers will instantly know what the files are used for if standard naming conventions are used.

Below each file or file type is a section that specifies whether the file is required for (program) Compilation or Application Deployment. Files are listed in alphabetical order by their file name extension.

Debug Information File (*.DBG)

When compiling a DataFlex project file (project.src), a file containing symbols and other debugging-related information is automatically created with the extension .DBG. This file is only used for debugging.

Required for:

  • Compilation: No
  • Application Deployment: No

Definition-Display File (*.DEF)

A rootname.DEF file is neither created nor updated automatically, and the tools do not use it. The rootname.DEF file is a plain ASCII file that contains a tabular display of a database table’s names, column names, types, and lengths, definition of indexes, etc. When you print a file definition from Database Builder, the printout exactly matches this table. This file can be used as a visual reference of an embedded database table's structure and to recreate an embedded database table from it.

Required for:

  • Compilation: No
  • Application Deployment: No

Compiler Dependency Check File (*.DEP)

The compiler maintains a compiler dependency check file for each project with the extension .DEP. Normally, the compiler looks for the compile dependency file and only recompiles if the compiled program is out of date with the source code. This option can be disabled with the C compiler option.

Required for:

  • Compilation: Yes
  • Application Deployment: No

Executable Program File (*.EXE)

A DataFlex project file is compiled into executable files with the extension .EXE.

Required for:

  • Compilation: No
  • Application Deployment: Yes

Compiler Error File (*.ERR)

If errors occur during program compilation, the compiler errors are placed in a file with the extension .ERR. If compiling a project inside the Studio, the compiler errors are automatically displayed in the Studio's output window.

Required for:

  • Compilation: No
  • Application Deployment: No

File-Definition File (*.FD)

The file-definition file also contains a list of the database table's columns, and the table's DataFlex name (the name by which it is to be addressed in programs, or "logical name") as well. This file links each column's name to the ordinal column number in the database table’s definition, and links the DataFlex name to the database table’s number in the Filelist. The file is required only for the compilation of programs that address a database table (embedded or not) and, although it is a plain ASCII file, it should not be modified by any means other than the tools. This file should not be deployed to end-users.

Required for:

  • Compilation: No
  • Application Deployment: No

See Also: The Filelist, Database API attribute DF_File_Logical_Name

Precompiled Program File (*.FLD)

When precompiling a program, a file which is exactly like a compiled program file is created with the extension .FLD.

Required for:

  • Compilation: No
  • Application Deployment: No

Precompiled Debug Information File (*.PBG)

When precompiling a DataFlex source code file, a file containing symbols and other debugging-related information is automatically created with the extension .PBG. This file is only used for debugging.

Required for:

  • Compilation: No
  • Application Deployment: No

Precompile Compiler Dependency Check File (*.PDP)

The compiler maintains a compiler dependency check file for each precompiled file with the extension .PDP. Normally, the compiler looks for the compile dependency file and only re-precompiles if the precompiled file is out of date with the source code. This option can be disabled with the C compiler option.

Required for:

  • Compilation: Yes
  • Application Deployment: No

Precompiled Debug Package Include File (*.PKD)

When precompiling a DataFlex source code file, a file containing other information about the file just compiled is automatically created with the extension .PKD. This file is only used for debugging.

Required for:

  • Compilation: No
  • Application Deployment: No

Package and Other Source Code Files (.PKG, .DD, .VW, .SL, .RV, .BP, *.WO)

When compiling a program, other files referenced in that main source file are also compiled into the executable file. Read more about package filename extensions here.

Required for:

  • Compilation: Yes
  • Application Deployment: No

Intermediate Code Listing File (*.PRN)

When compiling a program, a file containing intermediate code can be created with the extension .PRN.

Required for:

  • Compilation: No
  • Application Deployment: No

See Also: Compiler Options

Precompiled Intermediate Code Listing File (*.PRP)

When precompiling a program, a file containing intermediate code can be created with the extension .PRP.

Required for:

  • Compilation: No
  • Application Deployment: No

Project Source Code File (*.SRC)

A DataFlex project file, which is compiled into an executable file, uses the extension .SRC. In the Studio, new project files are assigned the extension .SRC, and existing source code files with the extension .SRC can be added as projects.

Required for:

  • Compilation: Yes
  • Application Deployment: No

See Also

Developing Database Applications