Help w.design

[teelee]

I need to build a database and I have alot of information that I need to use.
There are about different catogories and i'm not sure how to proceed with the
design. If I enter all the info into one table then the table will be too
large and I heard that access doesn't work well with large tables. What would
be the best way to design this database?

Thanks

 

[Duane Hookom]

This describes 1,000s of applications. You might need to provide more
specific information if you want to get specific help.

BTW: Access loves large tables (lots of records).

 

[Duane Hookom]

I just reviewed your table structures in another thread and you have grossly
un-normalized tables. I wouldn't go much further without normalizing.

 

[tina]

size is pretty much irrelevant, unless the table/database gets really huge.
but Access doesn't work well with *non-normalized tables*, that's for sure;
and tables with more than 20 to 30 fields (most tables have less, often
considerably less, fields) are almost always NOT normalized. recommend you
read up on data modeling now, before you build your tables, or you're going
to spend a lot of time rebuilding and/or fixing problems. for more
information, see http://home.att.net/~california.db/tips.html
beginning with Tips 1 and 2.

hth

 

[teelee]

Thanks for the reply..can you tell me how I would normalize my tables. I'm
new to databases.
Thanks

 

[Duane Hookom]

I posted some links in another thread to resources on the web. Check Jeff
Conrad's links from
http://home.bendbroadband.com/conradsystems/accessjunkie/resources.html#DatabaseDesign101.

 

[scubadiver]

"Normalizing" basically means that data should not be replicated in more than
one table.

 

[Duane Hookom]

That's a start but there is a lot more to normalizing.