Then a property has a house plan added to it, as some properties can have multiple homes on it. The property Table is going to be the main table, which will have a owner tied to the property. This would also include a pricing list obviously and many other tables that would be children of the house plan. I've attached an image trying to figure out how i should structure it in my head.
I was thinking maybe the only way was to have each item search the database for the exact product code, which seems the most logical. One main question i have in terms of doing the quotes is how would i link my data to the pricing table? As i can not guarantee that the list i get will always be in the exact same order, also if new products are added it would mess up any sort of id system i had in place. So that each new address can use that pricing to create the quote, once the quote is generated i can save that out to another table so the prices remain frozen for that period when the pricing was set.
I get a monthly database of prices emailed to me from my supplier in CSV format, so i would want to update that table in my database monthly also. I would like some advice on how i should structure all of this. This info will be used to create a quote from also. The general gist of this is so i can create a new property, From there the house plan is added for the property where then all sorts of details, like length of drains, type of roof, distances between areas can be added to children tables. I can also give links to the builder so he can track the progress of the property and the history. I've progressed well on my dashboard i'm creating for a plumbing business (My Own) we specialise solely in new homes, and i'm trying to automate a lot of the processes i currently have to do manually, mostly arbitrary paperwork and management of jobs.