Hi,
I'm in the process of improving one section of a database, adding a table of qualifications for the people in my people table. At the moment, the two important qualifications are listed as fields in the people table, with simple checkboxes to say if they have the qualification or not. I want to have a separate table listing the ID of each qualification event, the person, the qualification category and level, the date and centre, and an attachment for a scan of the certificate. So far, I've got two tables, one with the fields described above, and another with its ID, and fields for qualification type and level, the idea being that on the qualifications table, I have combobox fields for looking up person, which I've already implemented, and then lookups in the possible qualification and level, so from one box I select the category from all possible, and then in the level lookup, it only displays the possible levels for that category.
The rest of the fields I would then just enter manually.
Is that possible?
Many thanks.
Hi timbim,
Yes, what you describe is possible. However, you may be better off to use three tables; a people table, a qualification table, and a "child" table between the first two. The child table would hold the PeopleID, the QualificationID, and the completion date.
Cheers,
Docendo discimus.
Please consider:
- Thanking those who helped you. Click the reputation icon
in the contributor's post and add Reputation.
- Cleaning up when you're done. Mark your thread [SOLVED] if you received your answer.
That's essentially what I've already got, and I haven't expressed the problem very clearly. What I'm struggling with is the way to do the lookup on qualification type and level, so each qualification type is displayed exactly once, and then once one is selected, only the levels available for that qualification are shown in the level lookup.Originally Posted by ConneXionLost
Hi timbim,
Okay, time for a silly question. Are you doing this on a form, or are you trying to do it directly in the table?
If you're trying this in the table, then stop.
If you're trying this on a form, then you can use a subform, or synchronize the combo boxes like this:
synchronize
Cheers,
Docendo discimus.
Please consider:
- Thanking those who helped you. Click the reputation icon
- Cleaning up when you're done. Mark your thread [SOLVED] if you received your answer.
Is it not possible to do in a table? I've got other lookups running into comboboxes in tables happily enough, what's so different about the problem here?
Hi timbim,
Sorry for the delay, my work got in the way of answering here.
Perhaps it's me now who isn't being clear. I never said it wasn't "possible" to do what you're suggesting, and basic combo boxes in tables are commonplace; but if you commit all your validation and functionality at the table level, you may end up limiting yourself further on down the road. It isn't a hard & fast rule, just a preferred design approach to use forms for that sort of thing. (Admittedly, I've never tried to "synchronize" two combo boxes directly in a "table", and I'm not sure it would even be possible to do without a location to temporarily store the data before writing it to the recordset.)
Access forms are designed for this. They have all the functionality and features to accomodate (especially with the use of sub-forms) a wide range of possibilities for data entry that a table view just can't provide. On that note, if you read over the link regarding syncronization of combo boxes you may see what I mean.
Cheers,
Docendo discimus.
Please consider:
- Thanking those who helped you. Click the reputation icon
- Cleaning up when you're done. Mark your thread [SOLVED] if you received your answer.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
Reply With Quote
Bookmarks