I have two sets of data - a list of roads and a list of issues. For each road, each of the issues must be addressed.
I have previously designed a database that had a table for each of the data sets, and used an update query (from memory) to create a third table that combined the two - creating a record for each issue for each road (ie if I had 10 roads and 10 issues, the third table ended up with 100 records).
I have a new projects, with some different parameters to the original, so a completely new database is required.
Initially this project only required a yes/no response, so I used the roads table with a field for each issue. It looks like they'll be wanting a comments field after all, so I'm tempted to reinvent my previous design.
I'm just wondering, if the 'two merged tables' design I used last time is the best way to approach this issue.
I have previously designed a database that had a table for each of the data sets, and used an update query (from memory) to create a third table that combined the two - creating a record for each issue for each road (ie if I had 10 roads and 10 issues, the third table ended up with 100 records).
I have a new projects, with some different parameters to the original, so a completely new database is required.
Initially this project only required a yes/no response, so I used the roads table with a field for each issue. It looks like they'll be wanting a comments field after all, so I'm tempted to reinvent my previous design.
I'm just wondering, if the 'two merged tables' design I used last time is the best way to approach this issue.