| Column | Type | Length | Description |
|---|---|---|---|
| Location_ID | Number (Long) |
4
|
Unique ID for each location record |
| Address1 | Text |
25
|
Street address first line |
| Address2 | Text |
25
|
Street address second line |
| State | Text |
15
|
Street address state |
| City | Text |
20
|
Street address city |
| Zip | Text |
10
|
Street address zip code |
| Phone | Text |
20
|
Primary phone number |
| Cross_Streets | Text |
50
|
Cross street and landmark information to help with driving |
| Web | Text |
50
|
Internet web site address |
| Comments_ID | Number (Long) |
4
|
Record ID of any comments related to this location. (May be NULL) |
| Modified | Date/Time |
8
|
Timestamp when this record was last modified. |
| Modified_By | Number (Long) |
4
|
Record ID for the food detective that last updated this record. |
| Created | Date/Time |
8
|
Timestamp when this record was created. |
| Created_By | Number (Long) |
4
|
Record ID for the food detective that created this record. |
By way of the Availability table, these records are used indirectly by the Item and Establishment tables. Each record in those tables can point to one or more records in this table via the Availability table. That is a one to many relationship from those records to these records.
The Comments_ID field in this record can point to a record in the Comments table. This can be a one to one relationship between this table and to that table. If the user does not wish to add any comments about the Location, then this ID field will be NULL.
The Modified_By and Created_By fields in these records each point to single records in the Food Detective table. Because a food detective can create multiple entries in the database, this can produce a many to one relationship between these records and the Food Detective records.
Availability Table,
Comments Table,
Establishment Table,
Food Detective Table,
Item Table.Send comments and suggestions to:
DBA@AllergyFreeFood.orgHome | Documentation Last updated on 12/12/00