Thanks guys.
I wasn't very clear in my original email. I already
had a business section table (with a primary key). My
problem was, I couldn't figure out how to accurately
store (for information retrieval purposes) information
about business sections that use particular
applications. I was
This is, as you guess, a very basic issue for relational databases. You
never want to put multiple entries in one column, as you describe it.
That's the scenario in which you create another table and use a key to join
the two. For your project, you should have a column in the nms_apps table
that
You could do it many different ways. Here's one that I would consider:
Create a table to store the business sections (buss_section) and a table to
relate the apps with the business sections (app_buss_section). The design
would abstract the app info from its usage and create a manageable table of
