I am reviewing a medical solution which has 35 related tables (one for every kind of examinations each with their Price field) plus a specific related Table designed for various statistics about type of visits, examiners, related income, etc, sorted by Year.
The actual relationship graphic has many many table occurrences, each for every type of exam, example:
Then in the Statistics_Table each kind of statistics is showed using portals sorted by Year (10 years back).
The actual solution works (even if sometimes they report having crashes), but the relationship graphic is awful since all 5 table occurrences above are repeated for each of the 35 kind of examinations.
I guess there is a way for optimize everything but before making any change I wish to receive some inputs.