Intro:
I have been working on a Sports Card database and have many questions posted on this forum related to creating the database through MS Access. After some time (2 yrs) I have decided to enlist the help of an old work colleague who had experience with databases (SAP, Oracle, Postgres) because I could not understand how to write the queries over all these many to many relations in Access. I've just not made significant progress on my own to the point where I was becoming very frustrated.
Summary:
In our original discussions over database design (i.e. normalizing tables) we are just mapping things out visually in an excel file and I notice he has me creating a lot of what I assume will be lookup fields in some platform other than Access. I explained to him that these are many to many relationships that I previously planned out by using m2m joins as I had laid out in Access but he disagrees on this design and instead has me linking tables directly by linking a PK of one table into another table as a FK instead of having a join table in between.
Question:
Are lookup fields only an Access thing? I have drilled into my brain that lookup fields and multivalued fields are evils in Access but do both of these become more acceptable using another platform like Postgres or mySQL?
As always, thankful for anyone who replies!
I have been working on a Sports Card database and have many questions posted on this forum related to creating the database through MS Access. After some time (2 yrs) I have decided to enlist the help of an old work colleague who had experience with databases (SAP, Oracle, Postgres) because I could not understand how to write the queries over all these many to many relations in Access. I've just not made significant progress on my own to the point where I was becoming very frustrated.
Summary:
In our original discussions over database design (i.e. normalizing tables) we are just mapping things out visually in an excel file and I notice he has me creating a lot of what I assume will be lookup fields in some platform other than Access. I explained to him that these are many to many relationships that I previously planned out by using m2m joins as I had laid out in Access but he disagrees on this design and instead has me linking tables directly by linking a PK of one table into another table as a FK instead of having a join table in between.
Question:
Are lookup fields only an Access thing? I have drilled into my brain that lookup fields and multivalued fields are evils in Access but do both of these become more acceptable using another platform like Postgres or mySQL?
As always, thankful for anyone who replies!
Comment