Looking for suggestions & input

[jeremie_ingram]

Hey all, I am currently looking to make a great database system for use within my community. What I currently have is a mdb with just 3 tbls but will be building from there. I have the normalization down thus far, but wanted to put things out there for any suggestions or ideas to make this a useful system. This is not a profit situation, and will generally be used only by myself or possibly one or two others.

What I have is a database that tracks the homeowners within our community (subdivision) and their properties. So far I have 3 tbls

tblOwners
- OPkey (autonumber)
- OFname
- OLName
- OStAddress
- OCity
- OState
- OZip

tblUnits
- UnitPKey
- StNum
- Street
- PIN
- Check2005

tblJct
- UnitPKey
- OPKey

Structurally this works great so far. I can easily relate properties to their owners and link multiple properties to those who own more than 1 (landlords). I structured it this way since the two tbls had many to many relationships, so the junction tbl made the most sense.
Now I am looking to add information from a tract search (mortgage holder information) which technically relates to both of these tbls (Unit & Owner) as well. I already know that most of the owners with multiple properties will most likely have the same mortgage holder, but that is not definitive. Since the same mortgage holder could easily be associated to multiple properties within the community, I know I have to have an independent tbl for that information as well.
What I would like to head for is something that will allow me to send notifications, letters, flyers and the likes to either the owners, residents, mortgage holders, or any combination of the three. I have attempted to create a few thus far but have issues with getting all of the required data output to Word, so I am thinking I may need to design these items in a Form instead.

Any thoughts or comments would be appreciated. I know I am heading in the right direction, but just putting it out here for the Access community to put in their 2 cents.

 

[KenHigg]

If I may nit-pick a bit -

a. If you are going to preface the owner flds with 'O', you need to use that same naming convention in all of your tables.

b. If you are going to use StAddress, City, State, Zip in the owners table to identify a location, you should use that as your model in the units table instead of stNum and Street.

 

[jeremie_ingram]

I appreciate the thought, and will do that (it was on the agenda). The thing was that I received all of this data in one Excel sheet originally, so I simply placed the O to identify the Owner information within the queries. I will place it accordingly throughout the table.

As for the units table, each one will reside within the association and have the same city, state, and zip. The owners that are landlords can live just about anywhere so that additional information is required for mailing purposes. For the majority (80%) the unit and owner address will be one in the same.

 

[KenHigg]

One more thought, if I may...

Looking at the design, tblOwners seems to me to be more of a kind of 'owner detail' table. And the junction table then would morph into the actual 'Owners' table.

Using this perspective may help to see how other tables of data fit in...