jtrombley24
New Member
- Joined
- Feb 21, 2016
- Messages
- 27
I'm wondering what others might suggest for a project I'm working on.
Quick project summary: I'm working on an Excel Front-End (Spreadsheet, Forms, VBA - the whole thing) with an Access database.
The main form has a multipage control with about 35 total comboboxes. My question is related to how to best populate them:
The original file that I received (from the group that is requesting the 'automation') had a bunch of validation lists set up on a separate tab from their main data tab. As I was designing the form, my initial thought was to just use these lists to populate my comboboxes (with the .rowsource property). I set it up and it worked well - in fact really well in the form_initialize event.
As I thought about it, the .rowsource code is vulnerable because the end users could add or insert columns, thus completely destroying each combobox .rowsource 'binding'.
So I thought about going the ADO route (and in fact wrote the code for it - and it works well for a couple of the comboboxes I tested). The problem here is that I DON'T want 35 separate tables to manage in the database. I can put the lists in one table with 35 fields, but then this is tough to manage since each row is unrelated.
What do you all think!?
Thanks,
Jim
Quick project summary: I'm working on an Excel Front-End (Spreadsheet, Forms, VBA - the whole thing) with an Access database.
The main form has a multipage control with about 35 total comboboxes. My question is related to how to best populate them:
The original file that I received (from the group that is requesting the 'automation') had a bunch of validation lists set up on a separate tab from their main data tab. As I was designing the form, my initial thought was to just use these lists to populate my comboboxes (with the .rowsource property). I set it up and it worked well - in fact really well in the form_initialize event.
As I thought about it, the .rowsource code is vulnerable because the end users could add or insert columns, thus completely destroying each combobox .rowsource 'binding'.
So I thought about going the ADO route (and in fact wrote the code for it - and it works well for a couple of the comboboxes I tested). The problem here is that I DON'T want 35 separate tables to manage in the database. I can put the lists in one table with 35 fields, but then this is tough to manage since each row is unrelated.
What do you all think!?
Thanks,
Jim
