Design Conundrum

[memphiszen]

Hello all,

I'm designing a property management database. There are many properties. Each property can have 1 or more units. How should I go about creating tables for these? Should I create a properties table and a units table?

At first I thought I should just create one table called Units. Each record would be a combination of property name and unit#. For example, if there was a property on Smith street with 5 units, then in the Units table, there would be 5 entries, smith1, smith2, etc. But somehow I thought this would not allow me to query and report financial figures accurately or as easily. Thanks for any suggestions.

 

[David Eagar]

At first glance, a property table, linked one to many with a units table is the way to go.

Do some searches in the forum as I have seen examples/questions on property db's and the answer may already exist

 

[Rabbie]

Hello all,

I'm designing a property management database. There are many properties. Each property can have 1 or more units. How should I go about creating tables for these? Should I create a properties table and a units table?

At first I thought I should just create one table called Units. Each record would be a combination of property name and unit#. For example, if there was a property on Smith street with 5 units, then in the Units table, there would be 5 entries, smith1, smith2, etc. But somehow I thought this would not allow me to query and report financial figures accurately or as easily. Thanks for any suggestions.

This structure should make it easier for you to get Financial data both at the property levl and at the unit level. It's just a matter of writing the correct queries