Multiple Attendance Dates for each Record

[Guest]

I am in the process of creating a database the will track the attendance for
each student, and I would like to store all dates that each student has
attended class.

I am not sure how to design the date record leep part of my database.

Any suggestions, tips, ect...

 

[Duane Hookom]

You should create a table that stores the StudentID, ClassID, and ClassDate
for each student attending a class on a single date.

 

[Guest]

I have just been asked to create a database to hold student attendance. I
have not done this before. I know how to set up the tables and such...I am
just wondering how you are going about displaying the attendance marking
partion and per student. Is this all being placed on an Access "form" or do
you have to bring in VB? My people want it all to stay in Access.

 

[Duane Hookom]

Most of what you might need shouldn't require VBA. It would help if we had a
really good idea of what you have and what you want to accomplish.

 

[Guest]

Beginning stages, as of now the database contains only student info (name,
address, etc) we are now looking into adding the attendance tracking portion
to it. I was looking to see if 1st Access "alone" could perform this
attendance tracking. 2nd : the set up would be per student and not JUST
showing the date missed/attending school but down to the class hours having
missed. ex. this student missed 5&6 hour only on 02/10/06 .

 

[Duane Hookom]

You can store all of that information in Access. Prior to creating your
tables, you should have a good understanding of database design. Jeff Conrad
has some great resources at
http://home.bendbroadband.com/conradsystems/accessjunkie/resources.html#DatabaseDesign101.

 

[Guest]

I was actually asked to make a database which keep track of volunteer hours
and claims. My biggest problem is that to make things convenient we would
like to input the data per activity, and how many hours each member have
receive and claims they require. However the data we need after processed is
report and record per member, showing their hours and claims. I read the site
that they say this is a type of many to many relationship. However I don't
where I should start with this.

Jeff Yuen
(e-mail address removed)

 

[John W. Vinson]

On Mon, 10 Sep 2007 20:42:02 -0700, Jeff Yuen <Jeff

I was actually asked to make a database which keep track of volunteer hours
and claims. My biggest problem is that to make things convenient we would
like to input the data per activity, and how many hours each member have
receive and claims they require. However the data we need after processed is
report and record per member, showing their hours and claims. I read the site
that they say this is a type of many to many relationship. However I don't
where I should start with this.

Start with the table design. What Entities - real-life persons, things, or
events - does your application model? Well, let's see: there are Volunteers;
Activities; Hours; and Claims. Each of these should be a table (though I'm not
sure I understand what a "claim" might be!)

What does a record in each of these tables represent, and what information is
needed in it? Volunteers: VolunteerID; LastName; FirstName; other biographical
data; contact information such as phone number. Activities: ActivityID;
ActivityName; other info about the activity in the abstract. The core - the
many to many table - is probably Hours: it would have fields for VolunteerID
(who did the work), ActivityID (what they worked on), TimeWorked (probably a
Long Integer field storing minutes worked, to allow for 2 1/2 hours = 150
minutes). This would be related to the Volunteers table by VolunteerID and to
the Activities table by ActivityID, so that you could have a subform based on
hours on *either* a Volunteers form, or an Activities form, or both, depending
on whether you're focusing on an individual activity and want to see all the
volunteers, or vice versa.

I'm sure that the Claims can be handled in some similar way but since I don't
understand them...

John W. Vinson [MVP]