The simplest way may be the best, but I'm looking for a way that might be a bit cleaner...

I have a database that tracks office staff,space and network info. Well, right now it's mostly tracking staff and office space, but I want to work in the networking. Given our layout, each space has 1 (or more) data jacks. for most offices/cubes this is 1 to 4. For most of the meeting rooms this is 4-8, and for a few this could be up to 16 (training rooms).

Inititially I was going to make 16 columns in the table to allow for what might be the max number of jacks (also an issue, as this could possibly increase). To me this is a lot of dead space, especially since the data is attached to a Visio diagram that will list the info in each cell with a mouse over.

the Data Jack list is it's own table that also ties into the switch layout per floor (other info that we want to be able to track when having to do traces).

My next thought would be to make a text field that will append each added jack jack name (seperated by a ';' or other key char). This will make the list of the data easier to display, but issues arise when (though highly unlikely, except due to user error) data jacks are to be moved from one space to another. Yes unlikely, but this planing to be rolled out across Canada, and I would like the least amount of hiccups/headaches possible.

Any ideas on the best way to store this info in the table?