- Student info (such as First, Last name, address, contact #., etc)
- Student ID (Autoenter Serial#)
- Barcode– number (Barcode Tag)
- Student ID – number/ auto-serial number
- Check In Time – Time
- Check Out Time - Time
- Barcode (Barcode Tag)
- Transaction ID (autoenter Serial)
Make a relationship between these two tables Student::Barcode = History::Barcode
Now on a layout based on the Student Table, add a portal based on the History table and put into the portal the fields CheckIn and CheckOut.
Your scan IN should create a new record in the History table and set the CheckIn.
Your scan OUT should append the last record for that student in the History table and set the CheckOut.
The portal through to the student table will show all of the related records...not by Student, but by Barcode (assuming a barcode is per student here).
It's a good idea to have the autoenter Serial as StudentID, but for this function I think you actually want the relationship by Barcode.
While you're at this, consider how you'll handle lost cards...can you replace a card and give it the same Barcode?
And also consider folks signing each other in and out...c'mon, you did it in the student dorms too, right?
Food for thought...
Thanks for the quick and detailed response. We will try that procedure as soon as we get a hold of the scanner. We will keep in touch with you to extend our gratitude once that technique works out for us.
Thanks in advance and more power.