Form/Database design for monthly food distribution

[krazymike]

I work with a local community assistance program that distributes food to families once per month. What I'm trying to do is create a database (not the issue) with a simple method of inputting the attendance (where I'm having trouble) that is simple enough for the people who run the program (in their 60's +) to use each month.

My experience is extensive in VB6/VBA and C#. I'm just stumped on designing the form. We can use any version of Access for this. I'm thinking check boxes would be simplest, but my issue is that sometimes they're entering data from the last three or four months at once. I'd like the form to show the previous months' attendance so they can do this bulk entry. I just can't quite figure out how to maintain database integrity by using a one-to-many table schema and have these check boxes.

The other issue is that this is being run under the umbrella of a larger food distribution charity. They may come and ask for a printout of the attendance at any time. I would like to have a report that prints out like a spreadsheet with the name on the far left and a row of cells off to the right with "January 2013", "February 2013", etc as headers with an X or such in the column to show that they were there.

[Rabbit]

It's difficult to suggest a form design when we don't know your table design.

[Seth Schrock]

Not much information that really helps us understand the problem, but you might look into datasheet view for forms. They can even be used as subforms depending on your needs.

Can't really help you with the checkbox problem as we don't know what data will be behind those checkboxes.

And since you are just starting this, you should really look into Database Normalization. This will help you so that it is relatively easy to create reports. Spend the extra time in designing the database and you will be glad you did when you have fewer headaches to deal with.

Also check out the following links:
How to ask good questions
Posting Guidelines

[NeoPa]

Mike, you have to ask one technical question at a time here. Multiple questions may be asked, but in separate threads. May I suggest you check out the links posted and then think about posting a new question starting with the design of your data. Maybe you already have some good ideas on that, but we can also advise if you like. When you have a solid data base then a question on the form design will make much more sense and be more likely to result in a practical solution.

[zmbd]

krazymike:

Setting aside all of the site rules and guidelines that were overlooked in your post (yes dead horse, sorry :) ). Please take a look at the attachment in My post # 26 in this thread: http://bytes.com/topic/access/answer...esign-question . You should read the entire thread to understand what was going on; however, once you download the zip file from #26 and start the DB you should be able to figure things out.

Now the example database I've placed in post 26 WILL need some tweaking as I never intended it to be a "production " level database and I've a few changes to the code that might help streamline things; however, that is, possibly, for a different thread.

I also highly advise a simple review: A Tutorial for Access
I find that when struggling with something in DB design that often it's because I've "over thought" something (you know that Keep It Simple... rule) or I've messed up something in the basic design.