I'm not a fan for a few reasons;
- It can really become a beast to keep track of over time.
- It can cause performance issues if you have any reporting built off of the reverse portion
- Imagine all of the processing that has to go into, checking the summary field, then all the lookups, and possible summaries off of that.
- Especially when you get tens of thousands of records.
- Most if not all the reporting you need from a reverse relationship, can be done in the joined table with some preparation.
- Most people take it too far, and end up making multiple sequential reverse relationships, and then the issue just compounds itself.
I've inherited an app that had 10 reverse relationships between 2 tables, and the app almost couldn't run it was so bogged down.
