Hi Everyone, I am sure there are multiple posts and questions about this, but I just wondered if someone can help on the best way to structure the database.
Currently, where I have a many to many relationship, I use a joining table and then front end I have a ‘Do a search for’ - so for example I have an activity table, which holds the user, I then just present this front end with the constraint of any activity that equals current user.
Is that the best way of doing it? Or would it be better to store those activities on the user record as a list, then present as a list of Current User’s activities?
The two things I am mindful of (as I am sure everyone is), is the speed and also the workload.
Thanks,
Graeme