Rob,

It appears the point that you are missing is that each year an art show is a
different event although it may be the same venue. The year makes it
different. With this in mind, I suggest the following tables .....
TblArtShow
ArtShowID
ArtShowName
ArtShowAddress
ArtShowCity
ArtShowState
ArtShowZipCode
other fields you may need

TblArtShowEvent
ArtShowEventID
ArtShowID
ArtShowEventYear
ArtShowEventContact
contact fields you need
ApplicationDueDate
ApplicationFee
ApplicationSentDate
Accepted (Yes/No)
GrossSales
Expenses

Note that by recognizing each year an art show is a different event which is
recorded in TblArtShowEvent, application for the event is a one-to-one
relationship with the event so can also be recorded in TblArtShowEvent.
Similiarly, result is also a one-to-one relationship with the event so
result too can be recorded in TblArtShowEvent.

Steve




"Rob H" wrote in message
...
I've been working on this for some time and have yet to get what I need;
I'm
working on a db to keep track of art shows I apply to and attend, there
are
three tables:

Art Shows - contains ID(auto number), name, address, Contact , etc.

Application Data - contains ID(auto number), application due date, fees,
year applied, and accepted/declined.

Show Results - contains ID(auto number), gross sales, expenses, net sales

One show may have many application data entries(one for each year applied
to
as well as many show results for the same reason. The ID fields are set
as
Primary Key in each table, and I've tried various way of linking the
tables
with foreign keys set to number. When designing a query I either get an
error
message about the link being ambiguous or else it comes back with the
fields
I selected from the tables but with no records.

I'm out of ideas...