Delete objects

If you select an object in EasyMap (map object, analysis, table, query, territory structure), EasyMap automatically checks whether other objects depend on this object. It may therefore be necessary to delete other objects when deleting objects (deletion transfer).

If more than one object is affected by the deletion process, EasyMap displays a list of objects that must also be deleted. If you do not want to do this, you can cancel the deletion process at this point.

If a map element with sub-elements is deleted (e.g. a sheet or a map), all contained elements are automatically deleted. In this case, there is no explicit hint (if you delete a folder in Explorer, of course all files in it will be deleted as well).

In rare cases it may happen that an object cannot be deleted because a dependent object may not be deleted (for example, the objects of the territory organization may not be deleted with the EasyMap Standard Edition). EasyMap informs you of this with a message.

Examples of Deletion Transfer

• If a table is deleted, all analyses based on this table must also be deleted.
• When a territorial level is deleted, all territorial levels based on it and all map levels representing this territorial level must also be deleted.
• If a map is deleted to which an inset map belongs, this inset map will also be deleted. The same applies to a scale.
• If a map containing analyses is deleted, the analyses are also deleted.

Note: If you want to delete a map or table, but not an analysis based on it, use the command Database... to reassign the analysis to another table or map.