The extract file is represented in the model by a File element, which provides a pointer to a file.

For each extract file referenced in the logic of an EAESample model, a named extract file entity is created in the migrated (AB Suite) model. For example, if extract file ‘A’ is referenced in EAE, an extract file element with the name ‘AExtract’ is created in AB Suite. On migration, the logic is modified to refer to the named extract file. As described above, most of the LDL commands for processing extract files have been superseded by extract file built-in methods. When an EAESample model is migrated, any reference to a superseded command is replaced with a call to the appropriate built-in method.

For example: In EAESAMPLE’s SREPBYAREA report, the following LDL:

LOOK.UP; EVERY (SREP)
    DO.WHEN; SREP.MAINT NOT = (D)
        EXTRACT; SREP AS; A
    END;
END;
SORT; A ASC; A*SREP.AREA ASC; A*SREP.SALESREP
BEGIN.PAGE; 05
DETERMINE; ACTUAL A
    PRINT.FRAME; 10
END;

is migrated to LDL+ as:

LookUp Every SREP
	   If SREP.MAINT <> "D"
		   Extract SREP As AExtract
	   End
End
AExtract.Sort(Key(AExtract.SREP.AREA, "Ascending"), Key(AExtract.SREP.SALESREP,
"Ascending"))
BeginPage Frame05
Determine Actual AExtract
	  Frame10.Print()
End

There is a difference in the data format in extracted Ispec records in extract files that use the "Internal" Extract Record format between AB Suite for the Windows^® Operating System compared to Enterprise Application Environment 3R3 for the Windows^® Operating System. This is because the internal underlying technology is no longer COBOL based. Therefore, Ispecs extracted and retained in extract files using the “Internal” record format cannot be read directly by Agile Business Suite for Windows. This restriction does not apply to “Generic” format extract files or extracted Frames.