I
ITMA
I'm going nuts in trying to devise the basic tables and relationships for a
database to record details of property / real estate - commercial and
residential. I had in mind tables for
Sites (general locations such as office building at such and such a town -
assuming only one property per town)
Estates (ie whether the land is owned out right or leased, and the relevant
details for such)
People (self explanatory)
Companies (self explanatory)
Addresses (self explanatory - but thought to be necessary because one Site
might have more than address and more than one Estate - such as a Site at
London, an address of 1 Oxford Street that might be owned freehold, and 1a
which might be leasehold, and the whole - combined 1 / 1a might be leased to
a tenant.
On top of all of that, I'd need to log changes, like sometimes the street
numbering or post code changes, and people move companies, companies change
registered address, sites are sold or acquired and so on. This is to be my
first practical Access database and if the truth be known I've been trying
to work on it for a couple of years because I always hit problems. Not only
am I unsure, because I'm in a catch 22 with not knowing every aspect of
Access so not knowing how best to design the thing at the outset, as to what
tables are truly required and what are overkill, but its also occurred to me
that I'm clueless as to which of the many permutations of the various tables
and the relationships between them is the 'right' or at least optimal one.
Any ideas??
database to record details of property / real estate - commercial and
residential. I had in mind tables for
Sites (general locations such as office building at such and such a town -
assuming only one property per town)
Estates (ie whether the land is owned out right or leased, and the relevant
details for such)
People (self explanatory)
Companies (self explanatory)
Addresses (self explanatory - but thought to be necessary because one Site
might have more than address and more than one Estate - such as a Site at
London, an address of 1 Oxford Street that might be owned freehold, and 1a
which might be leasehold, and the whole - combined 1 / 1a might be leased to
a tenant.
On top of all of that, I'd need to log changes, like sometimes the street
numbering or post code changes, and people move companies, companies change
registered address, sites are sold or acquired and so on. This is to be my
first practical Access database and if the truth be known I've been trying
to work on it for a couple of years because I always hit problems. Not only
am I unsure, because I'm in a catch 22 with not knowing every aspect of
Access so not knowing how best to design the thing at the outset, as to what
tables are truly required and what are overkill, but its also occurred to me
that I'm clueless as to which of the many permutations of the various tables
and the relationships between them is the 'right' or at least optimal one.
Any ideas??