Chris, to expand on what Tom said... you will end up with two tables. If this is about users, and each user can have a variable number of research, the two tables will be like this:
user_info
user_id <- important: serial # assigned by DB
user_name
email_address
(etc)
user_research
related_user_id
research_name
research_details
(etc)
So when you go to look up a user and all their associated research, your code will do TWO things:
Fetch the user from the user_info table. Now you know their name, email address, etc, plus their very-important user ID number.
Fetch all rows from the user_research table WHERE related_user_id = the user_id you pulled from the user_info table in the previous step. See how this can return as many records as they have in the table?
To store info in the tables... just do the opposite ;-) Seriously, make the user an entry in the user_info table, then get their user_id and plug in each research piece into the second table, with the associated ID number on each row.
There's good article in the php builder archives on this very subject, called something like "normalizing your databases." Recommended reading ;-)
good luck,
Eric Mueller