gojets1721
Registered User.
- Local time
- Today, 15:31
- Joined
- Jun 11, 2019
- Messages
- 429
I've attached an example file, which hopefully will explain this better. Essentially, I'm using a calculated field to capture the data from over a multitude of columns. For each entry, there will always only be data in one of these columns and the rest will be blank. By using a calculated field, it pulls all the data across all the columns into one concise column. But this method is inherently flawed and the calculated field can't be edited in a form. I inherited this DB and it seems like this was a band-aid for poor DB design. In my example, you'll see that the subcategory field can't be edited.
The reason its likely designed poorly is because our IT team imports the data in, not me. They pull it from an online form and just paste it right into the table. Unfortunately, they won't change how they import it in or change their workflows.
Would anyone be willing to take a stab at how to construct the DB around this issue to basically allow the subcategories to be edited in the form? I've run outta ideas. Thanks
The reason its likely designed poorly is because our IT team imports the data in, not me. They pull it from an online form and just paste it right into the table. Unfortunately, they won't change how they import it in or change their workflows.
Would anyone be willing to take a stab at how to construct the DB around this issue to basically allow the subcategories to be edited in the form? I've run outta ideas. Thanks