db design

[Danny]

Greetings,
I just started a new position and assigned a new project to design a database using Access XP for a non profit organization.
They have four departments each with 5 to 10 employees. Some of them have to go out to a site and collect data and others collect data over the phone and manually enter them and give the report to their director every month (hand written report).
The directors then combine these report and fax them to the state every month.
Now my new job will be to design a database where by I'll run a report for each department(eg. Department #1 has a total of 25 records and entered by 'name of user' etc.) and another report (total report) for the stat (combining all four reports).
I kind of have an idea what I need but not sure how to go about creating them.
Please help!

Thanks in advance,

DD

 

[SQL_Hell]

I would go and buy yourself a book on access, it looks like you have quite a learning curve.

I realise this is not what you want, but what is the point of getting someone to design you an entire database, meaning you have learnt nothing.

As you start your project you may come accross problems, that is the time to post questions.

It is unlikely that someone here has the time to create a database for you.

Do a google search on Normalisation this should be your first port of call when considering table / relationship design.

 

[KenHigg]

Just be leery of some of advice you may get here... Most of the advice is great but some users should not be giving database advice (Just my humble opinion - Email some of the site admins on who to watch out for)

 

[SQL_Hell]

KenHigg

Does this mean you think I am one of these poeple?????

 

[KenHigg]

Surely you know of whom I speak...

 

[SQL_Hell]

No sorry,

I've only been active on these forums for a short amount of time.

So long as it aint me

 

[KenHigg]

Scan the 'DB_Size?' thread in the General forum...

No, I agree with your assesment of Danny's situation. Sounds like his boss needs to get out the check book and hire a db person if they need a solution anytime soon...

 

[Rich]

Don't make the mistake of having a separate table and report for each dept, you only need one to handle the data for all depts. Using parameter queries and or filters you can print a different copy of the same report for each dept. Do some searching here for normalis(z)ation before you start anything