Thanks to this website, and the help I've received in the forums, databases with web interoperablity is looking much clearer. I do have a design question that I can't seem to find the answer on, or the answers are not clear to me.
The background for my DB is this; I'm developing a training database for video, audio and documents. The application is Access with an ASP front end.
The issue with design is that I have a one to multiple relationship between offerings (video, audio and documents),to technologies (subject classifications), and objectives (planning, operating..etc). For example I have a document that covers operating and troubleshooting multiple pieces of equipment.
Here is an example of my table layout
tblofferings
offeringID, title, location
tbltechonlogies
technologyID, technology
tblobjectives
objectiveID, objectives
The issue is being able to relate multiple technologies and objectives to one offering. There is no maximum number of how many technologies and objectives that I can relate to each offering. I've tried creating an offering table with a yes/no for each technology, the issue with this is that it would become a huge table, which doesn't even bring the objectives into account. Another way would be to duplicate offerings with each one mapped to a the technologies that it requires. That option doesn't seem to be a good design.
Currently my offerings are at 300, technologies are approx 150, and the objectives are at 4.
Any assistance would be greatly appreciated. Thanks, Jeremy
Topic Options
Post Options
Thanks(0)
