Hello dear people from this forum, I really appreciate your valuable answers - I have learned a lot with all kinds of answers form this forum. Thank you!
I am struggeling with creating a good, consistent and logical database structure for my project. Maybe someone here can point me to a better direction:
I have built a multistep form - a business calculator - where a user can calculate his companies net worth by answering many questions.
Currently I have a single Data Type called financeinformation with about 30 fields (the answer to one question represents one field) like:
The calculator is not beeing finished yet and is likely to grow at least double.
Also I want to make some calculations in the background and this data will be saved as well e.g. the average of the last 3-year revenue or wheter the current year is the highest and so on…
What shoud I do? Should I create for each topic another Data Type within financeinformation and link to it? What is a good field-size? Are 60 fields too much for a bubble database?
What I can imagine to do is something like:
Does this make any sense?
Can you recommend any blog or book to study this?