Help with Tables (Full Version)

All Forums >> [Web Development] >> ASP and Database



Message

zappastixs -> Help with Tables (8/20/2003 10:06:01)

Hi

Advice please on the best way to set up a 'Web Directory'
using Access 2000 (via FrontPage 2000).

If I can get the project off the ground, it would eventually
have hundreds of 'categories'

This directory would search on standard links to categories
but at the same time provide users a search facility using
the keywords that web site owners have included in their
submission (I know it's been done before).

I worked out what I think would be the best way but this is
my first project of this kind and I would prefer to know if
you think I will run into problems further down the line.

This is what I was thinking of doing for the table layout

Under a main category for MUSIC – I have 3 Sub Categories
Songwriters – Pop – Rock

I have 3 Tables questions;

1) does the following layout look like it will work?

2) when a user submits data from ONE web form does Access
know where to place the data into the individual tables.

3) if a user were to search on just 'keywords' (KEYWORDS_tbl)
and a keyword matched a sub category (i.e. SONGWRITERS) would
the Web Address of that particular site(s) be displayed.


SONGWRITERS_tbl
Web_address_ID (key)


ROCK_tbl
Web_address_ID (key)


POP_tbl
Web_address_ID (key)


KEYWORDS_tbl
Keywords_ID (key)
Web_address_ID


SITE_DESCRIPTION_tbl
Site_description (key)
Web_address_ID



I hope I have made sense - I confuse myself sometimes.

Thank you in advance, Stephen



rdouglass -> RE: Help with Tables (8/20/2003 11:51:41)

If it were me and that was all the info I was using, why couldn't you put the category types into 1 table and use the category ID in the site description? It looks to me like you possibly could put your keyword list in there as well. Unless you have a ton of keywords that should be adequate.

I would even suggest maybe just 1 table to keep it simple. If you only have 3 categories, why couldn't you just use 1,2, or 3 in a column in the original table.

If you did that, maybe questions 2 & 3 are moot?

Or maybe I'm missing a bunch of stuff here?



zappastixs -> RE: Help with Tables (8/20/2003 13:28:09)

Thanks - I thought of that.

What stopped me is that if there
are say 1,000 categories and a
user selects the last category
wouldn't that slow the results
being delivered.

I'm just thinking out loud here
'cause I don't know if that would
happen or not.

If that were the case - would
indexing the Category help?

Thanks again - Stephen



rdouglass -> RE: Help with Tables (8/20/2003 13:51:05)

Ooops! Missed that about "100's" of categories. But I'm still unsure as to why you'd make a table for each category. How 'bout 2 tables?

I would also question the idea of 1000 categories. It sounds like you want them in a drop down menu? IMO that's a bad idea - takes too long to build the page.

Sorry, without knowing all the details, its difficult to design a DB scheme. Have you normalized your DB design? Don't want to insult your intelligence, but if you're not familiar with DB "normalization", you may want to take a look at this:

http://www.devshed.com/Server_Side/MySQL/Normal/Normal1/page3.html



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.09375