Database that has field that contains multiple values

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a database where one of the fields has multiple values (second column
PlanofRecord). There could be only one or many values with that are the
same.

Ex:
HICNbr PlanofRecord TROOP YTD TDS YTD AS OF DT
xxxxxxxxxA H0001 0 0 0
xxxxxxxxxA H0002 0 0 0
xxxxxxxxxb H0002 0 0 0
xxxxxxxxxC H0003 0 0 0
xxxxxxxxxD H0003 0 0 0
xxxxxxxxxE H0003 0 0 0
xxxxxxxxxF H0003 $11.62 $50.43 2007-03-04
xxxxxxxxxG H0003 0 0 0

I manually create tables for the PlanofRecord. Is there some way that I can
do this systematically? Create table H0001, H0002, H0003 etc.?
 
Theresa,
You really need to do some study on relational database design. You are way
off in the woods trying to create a monster.
Please understand my intent is to help.
The basic problem you have is creating multiple table that have similar data
and worst of all, one field containing multipe values.
It is difficult to tell from your description what it is you are trying to
accomplish. I don't know the author or publisher, but there is a good book
called Database Design for Mere Mortals (think the title is correct)
Do a little study and if you need additional help on this issue, I suggest
you ask your question in the Tablesdbdesign group.

Best of Luck to you.
 
Create table H0001, H0002, H0003 etc.?
Why would you want to create a table for each of this data? Please explain
a little more.
 
I have systems pull members that are going to another company. There could
be 10 people going to H0001, one person going to H0002 etc. I need to
seperate the H0001 from the other companies to send them only their
information. I know this is a monster. Maybe I need systems to create the
seperate files but I thought it might be possible to do it in access.
 
There could be 10 people going to H0001, one person going to H0002 etc.
I still do not see reason for separate tables. Maybe it is because I do not
see what you are doing with the data.
 
Theresa

The process ("how") you are describing sounds like what you'd do if you were
working with a spreadsheet.

Another way to handle this, and one that lets you take fuller advantage of
Access' relationally-oriented features and functions, would be to have a
single table that includes:

PersonID
GoingToH_ID (this would be an ID number like you've been embedding in
the tablenames "001", "002", ...)

I can't tell what else you are doing besides noting that PersonID=17 is
connected with GoingToH_ID=002...

If you'll describe a bit more about your "why" and "what", folks may be able
to offer ideas about achieving the underlying business need.

Regards

Jeff Boyce
Microsoft Office/Access MVP
 
Back
Top