I need help!!!!

[pablotx]

Howdy all,

This is my first post on your message board. I currently have been assigned to develop a database at my workplace to replace our current tracking system.
We are tracking assorted demographic information on people. Probably will have about 5-10,000 entries yearly. Myself and approximately 15 others will have entry privilege to the database which will be on the network. I will be the only one with Admin privilege. I am relatively new using Access. So I need your help. Here are my questions: 1) What is the advantage/disadvantage of using a few tables to collect data versus using one huge table? I was planning on having alot of of fields on one big table. I would base all of my forms, reports and queries off of it. About 50 fields, 15 reports & 15 forms. Each of the forms will have about 20 blanks on them and will sometimes be compiling duplicate data between different forms.
2) How can I make the system stable and safe from my computer illiterate coworkers?

I will probably be coming back to you regularly with more questions when I get further along in the process. Any suggestions or help that you can give me will be greatly appreciated. thanks

 

[directormac]

Just say NO to the "one big table" sceheme. It will only make life harder for you down the road. Search this forum on the words "normalization" and "design" separately. Check out O'Reilly's book on using MS Access - it covers design problems and why not to use one big table. Read up on Relationships, they're about to be your new best friend. Examine the included Northwinds sample database carefully.

Be patient. Keep slogging. It ain't always easy.

--Deja Mac

 

[chewy]

Pat,

In that microsoft link. I am not able to download the file. I get a page not found error. Is this just me? IS there a chance you have a copy I could get?

 

[chewy]

Thanks Pat. I wonder why I cant download though?

 

[chewy]

i shall try...thanks