Hi
Assuming i've understood your question correctly:

The usual way to tackle that is to have a user table, a hobbies table and a userhobbies table.

The user table would have a user id, each id representing one user (no way!) and the hobbies table has a list of hobbies each with a hobby id (no way!) and say a description or something. The user hobbies table just matches users to hobbies and would normally just be a two column table made of user id and a hobby id. Each user could obviously have multiple entries in that table pointing to seperate hobbies then you just do for example

select hobbies.description from userhobbies, hobbies where userhobbies.userid = X and userhobbies.hobbyid = hobbies.id

Then just loop through the recordset to get the result.

If you have heavy loaded server with very large results getting returned like that then you can use things like bitmaps to represent the data and get all your results from one returned row. It's not normally considered a very beautiful way of doing things (but beauty only matters in women imho :)