I will be interested to know how you will manage your provision of information accessed by a hyperlink and how you expect them to update the data around product recalls etc.
CJ, I expect that some but not all family members will copy blocks of text from the web into the database. This is why many of the textboxes are large enough for extra words and sometimes a second sentence. When I expect a lot of text to be pasted into a form, I use Long Text fields.
Information about food recalls is commonly a full page. It depends on the source of the information. To create a complete record, the person may need to use the CDC and the FDA websites after using MSN or Newsweek.
If a person copies the entire announcement into the database he/she won't be able to do certain searches. But with a little extra effort, the person can paste the symptoms of a disease into the correct box. And it is not required that all of the textboxes be used for a recall. I would suggest that a person always parse out the information for Class 1 recalls, but not always for Class 2 and 3 recalls.
To track the states where a product was distributed, the person won't need to type in state names. All he/she will do is check boxes on the recall map. That will be even easier if a person only wants to show when a product was distributed to their state. That will be the case if a person doesn't have relatives out of state. With no out-of-state relatives, the person really won't need the recall map form. That form can be deleted from the database. The person would use another form to enter information about recalls.
I have used as many click-to-enter Access controls as I can. Date fields use the pop-up calendars.
The Recall Map has 50 checkboxes for the states. Other checkboxes are for the types of illnesses, whether store receipts are required for returns, and on and on.
Many of the lists are MVFs, so they can reduce typing. The names of common illnesses and diseases use MVFs. The names of family members use MVFs.
Checkboxes, MVFs, calendars, and other objects are used throughout the database for finance and health. Some lookup tables are used in MVFs in both the finance and health domains. This is why there are currently 465 tables in the database. There are more tables than forms (455) because many tables are used multiple times.
If you develop a database with hundreds or thousands of objects, use as many click objects as you can. They will make it easier for your users. Which objects to use in your forms may not come to mind during design, so be open to adding them later. You will need the same objects in your reports, but they will frequently be in different places. Most times, I create several versions of forms and later copy specific ones into reports. I often consider reports to be more important than forms because they are distributed and used for decision-making purposes.
HTH.
Thanks for the comment.