I'm currently putting together a database for my work (not an expert by
any stretch, so muddling through as best as I can... you know the
story...) and I could use some advice and hand-holding
I've got a subform with a series of cascading combo boxes (thanks to
the Access tutorials on fontstuff.com) that let the user assign
categories to items, in this case photos. This is being done to help
constrain user selections and keep the categories being used as
heirarchical as possible. The VBA code has been written and seems to be
working perfectly for the cascading part of things.
Presently, there is a table underlying this subform with fields for
photo numbers and each of the four levels of the heirarchy (division,
class, category and sub-cat); the heirarchy entries are saved as plain
text. There are many records that are identical, except for the photo
number. (This probably means I should split off the possible
combinations of subjects into a separate table of their own, giving
them all unique "subjectId"s and then using another table to join
photoIDs and SubjectIDs together, but I'm not a purist,
philosophically... Anyway, there's alot of legacy data already in
there, and it would be a pain to try and split it off.)
Here's what I want to do: I want to add NotInList functionality to the
comboboxes this subform, so that additional items can be added to the
list at each level of the heirarchy, but only by having to click
through a warning dialogue. I'm hoping to adapt something like
http://www.fontstuff.com/access/acctut20.htm#fullcode for my purposes,
but this particular sample seems to assume that the source of the combo
box is a stand-alone table and I'm embarassed to admit that I'm much
more adept at adapting code than writing new code.
Is there anyone out there willing to hold my hand on this? I can
provide more detail about the existing code and data structure if
needed.
