Max fields per table?
I am working on a project management tool that stores projects, notes, sales data, and survey data. The survey data can be a lot of fields when we survey. To me I would think it should be isolated ...
Forum Discussion
Can you provide more detail? It sounds to me though that you will definitely want to use relationships.
For example
One Project has Many Project Notes.
I would need to hav3 a better description if the Survey to suggest an approach there. How many Questions? How many Surveys per project.
For example
One Project has Many Project Notes.
I would need to hav3 a better description if the Survey to suggest an approach there. How many Questions? How many Surveys per project.
Sure.... So for the project Notes that is a separate table that is related as a project does have many notes.
For the survey it is really more around data for a project. Each project has one set of survey data. For example, I will want to survey what electrical power is available in the building. 120 Volt, 208 Volt, 460 Volt, etc. And be able to select multiple options there.
So each project has one set of building survey data. Which ultimately might have 30-50 items on it. So that as we are designing we can continually update the data on what is available to us from an infrastructure in the building standpoint.
We are basically an architectural design firm, so looking to capture electronically all of the information our field people get when surveying a client site and be able to add to it as we coordinate with engineers and other people.
So each project has one set of survey data. And each set of survey data only belongs to one project. It could be all in the projects table. But I was wondering if that would be too much field wise for one table and we should have a one to one relationship?
I am envisioning all of this on a tab layout. So the first tab is the project overview. Project Name, client, project manager in the office, address, etc. Second tab being the notes on the drawing and a running discussion board of open topics. This third tab would contain all of the data around the survey.
For the survey it is really more around data for a project. Each project has one set of survey data. For example, I will want to survey what electrical power is available in the building. 120 Volt, 208 Volt, 460 Volt, etc. And be able to select multiple options there.
So each project has one set of building survey data. Which ultimately might have 30-50 items on it. So that as we are designing we can continually update the data on what is available to us from an infrastructure in the building standpoint.
We are basically an architectural design firm, so looking to capture electronically all of the information our field people get when surveying a client site and be able to add to it as we coordinate with engineers and other people.
So each project has one set of survey data. And each set of survey data only belongs to one project. It could be all in the projects table. But I was wondering if that would be too much field wise for one table and we should have a one to one relationship?
I am envisioning all of this on a tab layout. So the first tab is the project overview. Project Name, client, project manager in the office, address, etc. Second tab being the notes on the drawing and a running discussion board of open topics. This third tab would contain all of the data around the survey.