This thread has a mix of the OP's posting issues and his app, so it probably belongs in the General Discussion forum.
@DakotaRidge, adding new controls every time you add a new category indicates to me your data is not normalized. You should leverage subtyping and use cascading controls. Is there such a thing as cascading multiselect list boxes?
BlueSpruce, my data aren't normalized. When I ask folks if every table should be DKNF, no one ever ever says yes. Last week, my health database had 450 forms that were populated by more than 400 tables. This week, that database has 550 forms. On average, every table in the database has 20 fields. This is how I developed a database with 4000 tables, forms, and reports. I research a topic using textbooks, magazines, and the internet. I never know ahead of time what objects will be needed for a domain, i.e., category. So, I don't think that normalization is possible in my approach to database design. Doing normalization requires knowing where you are going and what you need ahead of time. My approach is one of Discover, Do, and Deploy. It is iterative because I often add new fields to tables, and I add new forms and reports as I go along.
To build out the health domains, I am using "Mosby's Manual of Diagnostic and Laboratory Tests (Sixth Edition)." For objects related to personal finance, I will mainly be using Dave Ramsey's "The Complete Guide to Money." Stores on MSN give me ideas, and I run with them. When I started this project, two friends told me about Quicken. Quicken doesn't work the way that I think. That's the power of Access, I can build a database my way. I must have images, analytics, and speech in my forms and reports.
I know nothing about cascading multi-select lists. I use MVFs in my objects. I use the MVF wizard that is part of the table definition tool, that's all. This is why I can create so many objects without code in a short amount of time. When MS accidentally removed the MVF wizard, I learned to deploy MVFs a second way.