the aim is store once, not store multiple times
Remember... Optimize 'til you die!
Progaming environment: Access based on my own environment: DAO3.6/A97/A2000/A2003/A2007/A2010 VB based on my own environment: vb6 sp5 ASP based on my own environment: 5.6 VB-NET based on my own environment started 2007 SQL-2005 based on my own environment started 2008 MYLE YOUR PASSWORD IS JUST LIKE YOUR TOOTHBRUSH DON'T SHARE IT.
Yes - providing that the application already 'knows' what the rest of the data is.
Out of curisoity what is the rest of the data you need to fill in? Are you sure you need to fill it in. (is having the employye ID good enough - remebering that you cna pull any inforamtion using a query providing that you gave its index / key value
The premise behind this form is that a user would enter in their employee ID and the then the form would fill in their name, department and pull any courses that they were already signed up for. That way they could edit what they were enrolled in or add an additional course in that form.
So I'd suggest unbound combo or list box with student ID (& name [ as secondary column]), and because of the high muppet count in universities / colleges another combo / list box showing surname, forenames and student ID. Not all students can remember what their id is (some don't even know what course they are on let alone what subjects they are on.
Design your form (probably form + sub form [for courses]) as normal (using bound controls). In the combo / list boxes place some code in the boxes on click event (list box) on change/click combo box.
You option call is to either set a filter
me.filter ="[StudentID]=" & cmbStudentID
me.filter ="[StudentSurname] like " & chr$(34) & cmbStudentName & "*"