Database Reference
In-Depth Information
F
IGURE
6.2
A f o r m t h a t i s f i l l e d o u t d u r i n g i n v e n t o r y t o e n s u r e a n a c c u r a t e
c o u n t o f t h e p r o d u c t o n h a n d
number when needed. One such product is guitars; this means that each
guitar, in this case, will need to be stored as a distinct entry in our product
table. We were told that some products are not stored by serial number. In
this case, we simply need to store a single row for that product with a count
on hand. Because it's not a good practice to break up similar data in a
model, we need to ensure that our model accounts for each of these pos-
sible scenarios.
Each form you look at should be examined for several things, because
each can provide you insight about the data and its uses. The following list
shows what you should look for and the types of information you can gar-
ner from each.
The data that the form contains
The data contained on the form gives you clues about what needs to
be stored. You can determine the data type, the format, and maybe
the length of the data to be stored. Seeing mixed alphanumeric data
■
Search WWH ::
Custom Search