View issue

currently, the delete function for an entry checks for child entry items before allowing the delete to proceed. However, since depreciation entry items for a given depreciable asset are usually recorded in a later, separate entry, those entry items are not considered. It would be best to prevent a user from deleting an entry when these related entries and entry_items exist in the database. otherwise, a member can delete the depreciable asset and leave orphaned entries and entry items in their books/the database.