Need help setting up a table!

[tina]

just a quick note, mabyn, to say sorry i didn't get back to you last night.
i've been pulling some 12- and 14-hour workdays last couple weeks, and some
nights i crash pretty early. you and Gina have a good dialog going in
another branch of this thread, though, and you're in very capable hands with
her, so i'll leave y'all to it.

 

[Gina Whipp]

Tina... you just need another cup of coffee And thanks for the kind
words!

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[mabyn]

Thanks Gina. The way it actually works is that I start by entering the
person/company in Attendees. Attendees table is people who at one time or
another have been in this parade. If they decide to be in this year's parade
we go to Registration (which is off of the Attendees form). There, things I
need to know about them registering are filled in. (Entry Name - This is the
Attendee kindof... If Sally Jones was the Attendee, her Entry Name might be
Krewe of Jones.) The database will have many Attendees but only the current
year parade participants will have an Entry Name and Registration number.
(All of that is attached to the Event Name which will change year to year,
payments, etc.) That part runs great (knock on wood.) After everyone has been
accepted to the parade that has registered (paid the bill, sent in a photo of
their float, sent in signed contract, etc.) we have a Safety Meeting. At that
meeting, each of these floats was assigned a place to arrive on Parade
Morning. That information is my LineUp Area (Areas). I wanted a combo box or
list box but obviously didn't create it correctly. At this point, each
registered ID & Entry Name knows their area to report to "this upcoming
Saturday morning <yipes>. I wanted to enter these into the computer so I
could generate a list by area for the Parade Marshals who check the floats in
could know who was supposed to be there. My Lineup table was just meant to
link things. Everything is tied together in my relationships. HTH

 

[mabyn]

Oh... What does pk and fk stand for?
--
Mabyn

Mabyn,

I see what you are trying to do but I can also see you have not fully
grasped relational database design.

The database for this parade is setup as follows now:
1. tblAttendees
aAttendeeID (PK, Autonumber)
aFirstName
aLastName
etc...

2. tblRegistration
rRegistrationID (PK, Autonumber)
rEntryName > Is this the Attendee?
rFloatOwner
etc...

3. tblLineUp
luLineUpID (PK, Autonumber)
luRegistrationID (FK)
luLineUpAreaID (FK)

4. tblLineUpArea
luaLineUpAreaID (PK, Autonumber)
luaAreas
etc...

Your form based on this set-up should be based on tblLineUp. Then you will
see who's lined up and in what area. You can use combo boxes for the two
FK's in the table. However you cannot add data to tblLineUp until there is
data to add from in tablLineUpArea and tblRegistration, that is if you are
creating relationships.

You can also review the below for basic database design..

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

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

A free tutorial written by Crystal (MS Access MVP): My favorite!
http://allenbrowne.com/casu-22.html

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

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[Gina Whipp]

Sorry, should have spelled that out... PK = Primary Key and FK = Foreign
Key (which is related to the PK).

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[¸¶·Ò·Ò]

you can use the soft named access

Mabyn,

Please explain the difference between Attendee and Entry Name so I can
help you.

Steve
(e-mail address removed)