ABL2DB parses one or more .dfs to build a set of tables which correspond to the schema, but are in ordinary files, not meta files. Then as it reads the XREF and the like, it can create links between the compile units and the schema, but the schema of the application (including any metaschema files accessed by the application), not the schema of ABL2DB itself.
Consulting in Model-Based Development, Transformation, and Object-Oriented Best Practice http://www.cintegrity.com
>> If you don't have any non hidden tables and select all of the hidden tables it instantly puts out an empty DF.
This issue is fixed in 11.5