Forum Discussion
_anomDiebolt_
Qrew Elite
Adding a large number of similar fields to a table is often a problem. The historic reason databases were normalized was to conserve storage and memory and to make querying faster. But it is much less of a problem today than it was in the past and there are many "non-SQL" databases that don't follow the conventional normalization rules (eg third normal form). Moreover, there may not be a need to break your data down into individual fields. Consider adding an address to your application. If you will only be using the address to print mailing labels you don't have to break your address up into fields and you can freely add text such as "attn: John Doe" and not disturb the schema of your address because the address is just one multi-line text blob.
I mention this because you could use just one field to represent all of your 100 pieces of data. Consider storing your data as a blob of text in CSV, XML, JSON or some other parsable format. When the form or page opens you could arrange for a script to run (onOpen) that would explode the blob of text data into a human readable format arranged as a table or grid of input controls and when the form or page closes you arrange for a second script to run (onClose) that would collapse the human readable information back into a original compact representation (CSV, XML, JSON ). This is much easier to do that you might think.
QuickBase might consider adding CSS, XML, JSON or even SCRIPT field types with appropriate API hooks such as onOpen, onClose etc. This may seem very adventurous but it is a lot easier to do than you might think. It sort of boils down to what your requirements are.
I mention this because you could use just one field to represent all of your 100 pieces of data. Consider storing your data as a blob of text in CSV, XML, JSON or some other parsable format. When the form or page opens you could arrange for a script to run (onOpen) that would explode the blob of text data into a human readable format arranged as a table or grid of input controls and when the form or page closes you arrange for a second script to run (onClose) that would collapse the human readable information back into a original compact representation (CSV, XML, JSON ). This is much easier to do that you might think.
QuickBase might consider adding CSS, XML, JSON or even SCRIPT field types with appropriate API hooks such as onOpen, onClose etc. This may seem very adventurous but it is a lot easier to do than you might think. It sort of boils down to what your requirements are.
NakiaHarringto1
6 years agoQrew Trainee
Hi Dan,
I only need 10 fields and not 100 fields. Is there a way to reduce the number of fields in the code.
I only need 10 fields and not 100 fields. Is there a way to reduce the number of fields in the code.