Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

Why does the CRUD report NOT show any Natural/ADABAS database access?

Why does the CRUD report NOT show any Natural/ADABAS database access?


In a project with Natural/ADABAS programs loaded and verified, the CRUD report fails to capture Table and File operations, such as UPDATE/FIND/STORE statements. Why does this happen?


This is caused by an incomplete project.

If a Natural program reads from a certain ADABAS file, then the corressponding .DDM is expected by Enterprise Analyzer.  If the file is not in the project, the database / file access is not shown on the CRUD report.

All items/entities of the project are expected to be available in Enterprise Analyzer, so that the correct relationships can be created.  

The DDM is required to complete the relationships to the database, if it is not present in the project, then CRUD cannot report correctly.

By making sure all required items/entities are included in the project, the CRUD report will contain the required information.






Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Version history
Revision #:
1 of 1
Last update:
‎2014-04-15 13:48
Updated by:
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.