Hi Kathy,
If you post back, tell us what you already have. Our answers quite
often depend on knowing where you are in your development and what
you've done to get there. Another thing that would help in "newbie"
questions is your motivation. Do you simply want a quick and simple
solution to your present dilemma or are you committed to learning
Access and this is just a project along the way?
To your issue:
A separate table is required for the seats. Each record in that table
needs a primary key (I recommend Autonumber); SeatName, Text (even
though you see it as number); IsAssigned, Yes/No; Note, text
tblSeat will be the many side of a one-to-many relationship with your
~main table.
The most useful paradigm for dealing with those one-to-many
relationships is with a form/subform construct. Access Help and the
supplied wizards are very helpful in getting this done.
You need a means in your order form to show seats by: All, Unassigned,
Assigned. People might call in after an initial order and request
adjacent seat(s). To accommodate you might have to de-assign their
earlier assignment and find a block of unassigned seats that meet the
new requirement.
If you just want an immediate solution to your present issue then I
suggest googling on related terms to find candidates. Also google on
terms like "demo software". You'll get a lot of hits. I know that
www.simtel.com has a lot of demo and freebie stuff.
If you want to get into Access beyond "newbie"{ status then I suggest
that you continue to lurk these Access newsgroups. In particular:
microsoft.public.access.gettingstarted
microsoft.public.access..tablesdesign
Also, pay a visit to
www.mvps.org/access and spend some time there.
Read what you can understand and pass by what you can't.
Welcome to the world of Access!
HTH