What is the W file format?
The .w extension identifies a GUI window or dialog procedure written in OpenEdge ABL (Advanced Business Language), the proprietary 4GL language developed by Progress Software Corporation. Unlike the general-purpose .p procedure file, a .w file specifically defines an interactive client window - frames, widgets, and event triggers - for the OpenEdge GUI client.
Files generated by the legacy AppBuilder visual designer contain &ANALYZE-SUSPEND and &ANALYZE-RESUME preprocessor comment blocks that allow the designer to round-trip the source without corrupting hand-written code. Modern development uses Progress Developer Studio for OpenEdge (an Eclipse-based IDE), though the .w convention remains unchanged.
A .w source file is plain text editable in any editor but must be compiled by the ABL compiler into a .r r-code binary before deployment. The OpenEdge runtime loads .r files; source is not required at runtime.
Key structural elements include:
DEFINE VARIABLEdeclarationsCREATE WIDGET-POOLand widget creation blocksONtrigger blocks wiring events to ABL logic&ANALYZE-SUSPEND/&ANALYZE-RESUMEsections (AppBuilder-generated only)
The .w file is distinct from .p (general procedure), .i (include/header), and .cls (ABL class) files. OpenEdge supports deployment on Windows, Linux, and Unix platforms, making .w files portable at the source level despite their GUI-oriented content.
Security & safety
RISK: LOWPlain text source code file; no direct execution risk. ABL code runs only inside the OpenEdge runtime. Standard code review practices apply when handling unfamiliar .w files from external sources.
Format details
in a nutshell- Ashton-Tate Applause Chart File - Obsolete 1980s-90s DOS presentation/charting software; the db_name in the database; entirely distinct from Progress ABL.
- Lynx/old browser form-fill data - Some older web browsers used .w files for form data; essentially obsolete.
Programs that open W files
Technical details
deep spec| Language | OpenEdge ABL (Advanced Business Language) - Progress 4GL |
| File role | GUI window or dialog procedure (client-side interactive UI definition) |
| Encoding | ASCII / Windows-1252 (legacy); UTF-8 in OpenEdge 11.6+ |
| Compiled output | .r r-code binary produced by the ABL compiler; required for runtime deployment |
| AppBuilder markers | &ANALYZE-SUSPEND / &ANALYZE-RESUME preprocessor blocks enable visual designer round-tripping |
| vs .p extension | .p = general or batch ABL procedure; .w = GUI window/dialog procedure only |
| vs .i extension | .i = ABL include/header file with no execution entry point |
| Typical content | DEFINE VARIABLE, CREATE WIDGET-POOL, frame definitions, ON event trigger blocks |
| IDE support | Progress Developer Studio for OpenEdge (Eclipse-based); AppBuilder (legacy visual designer) |
| Preprocessor syntax | &SCOPED-DEFINE, &GLOBAL-DEFINE, and {include.i} include syntax supported within .w files |
| Platform | Windows, Linux, Unix (AIX, Solaris) - source portable; .r r-code is platform-specific |
| Typical size | 1 KB - 500 KB |
| Container | Plain text - no binary wrapping or compression |
| Migration note | Modern web UIs (WebSpeed, PASOE, Angular) use .p files; .w is specific to the classic OpenEdge GUI client |
| Released | ~1994 (Progress 4GL; .w convention solidified with GUI builder ~v7-8) |
| Latest version | OpenEdge 12.x (2023+; ABL language unchanged in core syntax) |
| Specification | documentation.progress.com |
W conversions
Community Q&A
asked by usersNo questions yet - be the first to ask about W files.