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 from the other data as it is of a completely different type. i am not tracking addresses and sales data but now engineering data.Do I create a one to one relationship in a new table? can quick base support that? Or am I overthinking and just load the table up with fields and use tabs to keep my forms in order?

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.

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.

I do not recommend hard coding 30 to 50 fields on the project record for the survey questions. You should have a model project(s) with a child table of Standard Survey Questions.Then use the Copy Master Detail wizard function in App management to create a button which will copy those questions into your Project.I don't have time right now to go into a lot of detail, but I will come back to this question when I have time.Here is some help on that.https://help.quickbase.com/user-assistance/copy_master_detail.htmlfeel free to post back if you have questions.

So not sure if my request was clear as this isnt making 100% sense to me....All of the survey data is the same for every project. It is the same list of questions each time. The answers are sometimes not always available at the start of the project so we continue to feed the survey with new information as we learn it.That is why I was thinking they are all table fields. I am not quite following who or why I would use a copy records button?

Well if the questions are going to be identical for every project and yes you can have individual fields on the project record. This could all be on a tab on the project record. I had assumed maybe that every project would have a semi standard list of questions but there would be different questions for certain projects. So having a child table would let you customize that list of questions.

Max fields per table? | Qrew Discussions

QuickBaseCoachD
Qrew Captain
6 years ago
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.
- IvanWeiss
  Qrew Captain
  6 years ago
  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.
- AustinK
  Qrew Commander
  6 years ago
  I've seen tables with over a thousand fields and I'm sure people out there have more than that. Once you get over a certain amount it does become much slower and you have to really work with the form to make it still function well. At 50 fields you are not in danger of bad performance.
- IvanWeiss
  Qrew Captain
  6 years ago
  Got it, I am sure it might be above 50 as that wasnt meant to be literal. But it is far from thousands. I keep on expecting Quick Base to be less capable than I guess it really is! Thats a good thing!
QuickBaseCoachD
Qrew Captain
6 years ago
I do not recommend hard coding 30 to 50 fields on the project record for the survey questions. You should have a model project(s) with a child table of Standard Survey Questions.

Then use the Copy Master Detail wizard function in App management to create a button which will copy those questions into your Project.

I don't have time right now to go into a lot of detail, but I will come back to this question when I have time.

Here is some help on that.

https://help.quickbase.com/user-assistance/copy_master_detail.html

feel free to post back if you have questions.
- IvanWeiss
  Qrew Captain
  6 years ago
  So not sure if my request was clear as this isnt making 100% sense to me....
  
  All of the survey data is the same for every project. It is the same list of questions each time. The answers are sometimes not always available at the start of the project so we continue to feed the survey with new information as we learn it.
  
  That is why I was thinking they are all table fields. I am not quite following who or why I would use a copy records button?
- QuickBaseCoachD
  Qrew Captain
  6 years ago
  Well if the questions are going to be identical for every project and yes you can have individual fields on the project record. This could all be on a tab on the project record.
  
  I had assumed maybe that every project would have a semi standard list of questions but there would be different questions for certain projects. So having a child table would let you customize that list of questions.

Forum Discussion

Max fields per table?

Related Content

Jinja Max Value of a Field

Rearrange Fields/Columns in table

Snapshot Fields

How to relate two tables with the key to a third table?

Child Table Field Question