- My Forums
- Tiger Rant
- LSU Recruiting
- SEC Rant
- Saints Talk
- Pelicans Talk
- More Sports Board
- Fantasy Sports
- Golf Board
- Soccer Board
- O-T Lounge
- Tech Board
- Home/Garden Board
- Outdoor Board
- Health/Fitness Board
- Movie/TV Board
- Book Board
- Music Board
- Political Talk
- Money Talk
- Fark Board
- Gaming Board
- Travel Board
- Food/Drink Board
- Ticket Exchange
- TD Help Board
Customize My Forums- View All Forums
- Show Left Links
- Topic Sort Options
- Trending Topics
- Recent Topics
- Active Topics
Started By
Message
re: Any Microsoft Access Experts?
Posted on 1/17/14 at 12:32 pm to Doldil
Posted on 1/17/14 at 12:32 pm to Doldil
So the main database will have all of the alumni info tied to the unique ID. I then have completely separate tables for the the competitive teams. The only info I would like to go from the main database to the competitive teams is the unique ID and the first name + last name. That way queries will be easy to run.
Posted on 1/17/14 at 12:37 pm to TheOcean
quote:
So the main database will have all of the alumni info tied to the unique ID. I then have completely separate tables for the the competitive teams. The only info I would like to go from the main database to the competitive teams is the unique ID and the first name + last name. That way queries will be easy to run.
Maybe use a query with a join putting the only the data you want as a join between the two
Posted on 1/17/14 at 12:46 pm to TheOcean
quote:
So the main database will have all of the alumni info tied to the unique ID. I then have completely separate tables for the the competitive teams. The only info I would like to go from the main database to the competitive teams is the unique ID and the first name + last name. That way queries will be easy to run.
If the first and last names are already in your main table, then you don't need to duplicate them in your team tables.
And are you making a separate table for each team? If so, you might consider making a 'teams' table that gives each team an ID (so it would just need an ID column and a name/description column), and then a table called something like 'alumni_teams' that just has two columns, one for alumni ID and one for team ID, which as someone else mentioned would just reference the foreign keys in the alumni and teams tables.
Popular
Back to top
![logo](https://images.tigerdroppings.com/images/layout/TDIcon.jpg)