RolandGomez

Database Design

Discussion created by RolandGomez on Oct 3, 2016
Latest reply on Oct 4, 2016 by RolandGomez

Hello all,

     I need to pick your brains a bit. If I had to rank myself...meh, upper level novice. So here's my inquiry (this involves a Property Tax Consulting Service) and is there anyway around this. I have had to create the following:

     A) Client

          B) Client owns property(or properties)

               Each property has an assessed value and it is our job to reduce that value...so the also have a reduced value. Here's the kicker, these values change from year to year. So this is a small example of what is in my tables consist of the following

 

               2013_Assessed Value     2013_Reduction value

               2014_Assessed Value     2014_Reduction Value

               2015_Assessed Value     2015_Reduction Value

               2016_Assessed Value     2016_Reduction Value

 

    So the problem with it is that every year these fields need to be created and it's important to have year to year information because we utilize the previous years to track trends. Currently I have 338 fields and this next month I will create 2017 through 2019. So you can see how this database will continue to grow.  Is there anyway to get around the creating of new fields for every single year???

 

Just a shot in the dark and hoping you guys can throw me some ideas. Thanks for any help in advance!

 

-Roland

Outcomes