Hi Kyle,At the heart of many database applications is contact information. Your Properties have contact information too!I would create a table for Addresses, as your instructor suggested. Each of those Addresses will have an Autonumber field called AddressID, AddrID, or what you decide. It will be the Primary Key.In your PropertyInfo table, you can include a foreign key to the Addresses table by adding this field:-AddressID, Long Innteger, Address, FK to AddressesYou can then create a relationship from AddressID in Addresses to AddressID in PropertyInfo. The PropertyInfo table will also have other information about the property such as when you bought it, how big it is, etc.A Property can only have one address. An Owner, however, could have more than one ... home, work, vacation, ...I discuss contact information in my free Access Basics book, which you can find on Bill's site:Bill Mosca's MS Access Tools, Code and Samples
and in my Learn Access videos: Learn Access By Crystal - YouTube~~~the word "lookup" is also used to refer to a table with values to pick from, such as a list of Fee Types, as opposed to the lookup fields that should be avoided. Lookup fields mean the Data Type columns says "Lookup Field" in the table design.Warm Regards,CrystalRemote Programming & Training -- connect to me, let's built it togetherThrough sharing, we will all get better~ have an awesome day ~
Posted by: strive4peace2008@yahoo.com
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (2) |
Tidak ada komentar:
Posting Komentar