I’ve been trying to hash out the following problem for a while, but I think there is some fundamental concept I’m not getting.
I am creating the attached database to manage various projects a certain organization is funding. One project may take place in more than one city, have more than one special consideration, or fall into more than one category. Likewise they could have none of these. Also, there are an infinite number of possibilities for cities, special considerations and categories. To clarify, right now we only have projects in Athens, Hamburg, London, Capetown, Johannesburg, Dallas and Seattle, but tomorrow a new project could take place anywhere else like Preston or Perpignan, who knows.
The problem is that when I run a report or a query I have the same project listed several times (each instance where there is a different city, special consideration or category). I thought that relational databases and the unique identifier concepts were supposed to eliminate this problem. I’ve attached the database for reference. The query I ran was to show all projects, including their special considerations and categories, in London or Dallas. When I ran the report it listed the same project every time a special considerations or category changed (e.g. Project 11, ID: JFIT010). Originally I had created one to many relationships between the projects and the cities, special considerations and categories believing that for every one project reported on there would be many cities, special considerations and categories listed. It was then suggested to me to create the relationships I have currently, but then this messsed up my Forms.
Apparently I’m way off base can someone help?
I am creating the attached database to manage various projects a certain organization is funding. One project may take place in more than one city, have more than one special consideration, or fall into more than one category. Likewise they could have none of these. Also, there are an infinite number of possibilities for cities, special considerations and categories. To clarify, right now we only have projects in Athens, Hamburg, London, Capetown, Johannesburg, Dallas and Seattle, but tomorrow a new project could take place anywhere else like Preston or Perpignan, who knows.
The problem is that when I run a report or a query I have the same project listed several times (each instance where there is a different city, special consideration or category). I thought that relational databases and the unique identifier concepts were supposed to eliminate this problem. I’ve attached the database for reference. The query I ran was to show all projects, including their special considerations and categories, in London or Dallas. When I ran the report it listed the same project every time a special considerations or category changed (e.g. Project 11, ID: JFIT010). Originally I had created one to many relationships between the projects and the cities, special considerations and categories believing that for every one project reported on there would be many cities, special considerations and categories listed. It was then suggested to me to create the relationships I have currently, but then this messsed up my Forms.
Apparently I’m way off base can someone help?
