[AccessD] Presenting data problem

Well, the boss is simplifying things a great deal. All she really wants is
to track vaccines and vet visits. For vaccines, I'll need to know what
vaccines are expected and track when they're due and when they're applied.
For the vet visits, just date, comment, and the ability to scan lab
results. Getting all those vaccines by species will be the hard work -- but
the structure for it won't be so bad.

Susan H.


>
> Based on that experience, my only comment would be to trend towards
> discrete
> tables as much as possible in your design.  While the EAV design has its
> uses, it has short comings as well.
>
> Arthur's setup is a good in that your still using tables more or less, it's
> just that you have multiple tables stored together and in doing that, save
> yourself some work.  But really without much extra effort, you probably
> could bust a lot of that out into separate tables.
>
> I might also suggest that to cover the "loose ends", consider adding a
> diary/comment system (ie. "Lab notes") with a keyword search on it.   It's
> not typically something I like to do in a design because users start
> putting
> everything and anything in there and it's all free-form, but sometimes it
> is
> one way to get the job done.
>
>