I'm revamping a fairly complex database (anchor-buoy, separated-data-model, 300+ table occurrences). There are a number of root table occurrences that refer to the same table but are distinguished by access level.
In other words, based on the Students table, there is a root table occurrence Students_SV (for a student's view of their record) and a root table occurrence Students_AV (admin view of a student's record) . Then there are separate layouts for Student View and Student Admin view which each refer to their respective table occurrence. This seems unnecessarily complex (there is a lot of redundancy between the Students_SV and Students_AV table occurrence chains). Is there any reason not to just use the Students table as the table for both Student View layout and the Admin layout for viewing Students? If, say, there are relationships that you only want accessible to an Admin, isn't simply not including them in the Student view layout enough security?
Thanks for any advice!