Forum Discussion
QuickBaseCoachD
8 years agoQrew Captain
I think that you need to rethink the structure of your tables. If the data you are entering is really one for one with the Project record, then that data just belongs on a Form in separate sections, or even separate Tabs, now that we have Tabs.
If the Projects details are really child records, such as Tasks, then the best user experience will be to enable an option on the Advanced Settings for the Projects Record which say to save automatically when adding a child record.
So the user will just stat to do the data entry on the project record and when it comes time to add a true child, they will click ADD Task and the Parent Project record will save automatically. When they save the Task it will return to the Project.
If the Projects details are really child records, such as Tasks, then the best user experience will be to enable an option on the Advanced Settings for the Projects Record which say to save automatically when adding a child record.
So the user will just stat to do the data entry on the project record and when it comes time to add a true child, they will click ADD Task and the Parent Project record will save automatically. When they save the Task it will return to the Project.
ArchiveUser
8 years agoQrew Captain
For us 1 Project has many (rotating) Contacts & potentially different Companies (if the project is sold), _many_ Tasks that start from various points depending upon what the project chooses to do, and there are many Communications with various people. That was the reason for the multiple tables.
Maybe I will take a look with a fresh eye, or a coworker that is not involved but is database knowledgeable, to see what happens.
Thanks.
Maybe I will take a look with a fresh eye, or a coworker that is not involved but is database knowledgeable, to see what happens.
Thanks.