file for each dataset used by the application. When a process is compiled, the data structures are "bound" to the process at that time thus "binding" of data structures takes place at the precise moment the process is compiled. Because the structure and key structure files are kept separate, the dataset definitions can be altered during development. This is a major strength of CorVision allowing for a prototyping environment where both code and data structures can be changed throughout development then brought together at compile time. The structure and key structure files are loaded before the process is compiled. This is done by the load file. BUILDER makes the assumption that the data structures are already loaded when it compiles a process. It is at this point that the compilation "binds" the data structures to the code. Creating a procedure Add / Change the procedure specification (Progressively) Construct the application components Menus Screens Reports Custom Code (Progressively) Generate the compilable files Compile the procedure After generating the procedure The following files are created: .DEF :Define fields used within the procedure. .DFS :Define (.DEF) files used within the procedure. .DO :Generated BUILDER for controlling the running / compiling of the procedure. .IOS : the procedure. .LOA :Generated BUILDER for controlling the loading of all required datasets used by the procedure. .SCS :List of all screens used in the procedure The following files can also be added: .DCL :DIGITAL command language file. Define specific CorVision logicals. Define any other processing before the procedure is run. The following files are created after compiling: VAX 32 bit .SAV .EDO ALPHA 64 bit _TV.SAV (after vesting) _TV.HIF (after vesting) _TV.EDO (after vesting) References CorVision History on CV2VB web site Fourth-generation programming languages