You're being led astray by MS! Don't use multivalue fields. You
didn't mention them but also don't use Lookup Fields in tables.

Tables hold records of entities. A date is rarely an entity. More
commonly, dates show up as attributes. So don't create "date" based
tables. You are interested in dates but only in the context of an
entity: such as *when* did something happen to *what*. You are more
likely tracking the What.

Your schema (tables and relationships) should reflect the real world
enterprise or thing that you're trying to model and track.

A list of Access resources cribbed from MVP John Vinson follows.
It's huge and intimidating but pick something easy and get started.


Jeff Conrad's resources page:
http://www.accessmvp.com/JConrad/acc...resources.html

The Access Web resources page:
http://www.mvps.org/access/resources/index.html

Roger Carlson's tutorials, samples and tips:
http://www.rogersaccesslibrary.com/

A free tutorial written by Crystal:
http://allenbrowne.com/casu-22.html

A video how-to series by Crystal:
http://www.YouTube.com/user/LearnAccessByCrystal

MVP Allen Browne's tutorials:
http://allenbrowne.com/links.html#Tutorials

HTH
--
-Larry-
--

"Wendy" wrote in message
...
I am trying to set up a database for multiple projects. One of the
fields
can have multiple entries (Year format). When I try to query for
one year,
the results don't include any of the projects with multiple entries.
How can
i make this work? Do I need to make a separate field for each year?