Without a DB schema, it's going to be hard to follow your example very well - and difficult to run it on Access from my Mac :-p
(Once we have a schema we could, in theory, have it running in any old database - which opens up your options somewhat - although I realise you'll only be running it on Win32).
Looking at DatabaseTypes.bmx, are you planning on loading all the data in at once, or will you be retrieving only the bits you need when you need them?
Caching is fine for "static" data (that which doesn't change very often), but for more volatile information there's no harm in only having it in memory when you need it. As you probably already know ;-)
SelectorTypeID : Is this going to be used to help you find things listed under a specific category? (eg. Companies)
Where you would have another table with SelectorTypeID as a foreign key...
So...
User clicks on "Companies" in the list box, you then select from the db all the matching data for that ID.. and put it into your other list. ?
(although you would replace "*" with the list of columns, for readability :-p )
I think David's onto the right idea about initially populating the listbox. Add to the listbox after it's been created. It also means you should never need to edit the generated UI file :-)
MVC... Keep the data model separate from the User Interface.
(Once we have a schema we could, in theory, have it running in any old database - which opens up your options somewhat - although I realise you'll only be running it on Win32).
Looking at DatabaseTypes.bmx, are you planning on loading all the data in at once, or will you be retrieving only the bits you need when you need them?
Caching is fine for "static" data (that which doesn't change very often), but for more volatile information there's no harm in only having it in memory when you need it. As you probably already know ;-)
SelectorTypeID : Is this going to be used to help you find things listed under a specific category? (eg. Companies)
Where you would have another table with SelectorTypeID as a foreign key...
So...
User clicks on "Companies" in the list box, you then select from the db all the matching data for that ID.. and put it into your other list. ?
SELECT * FROM otherTable WHERE selectortypeid = ?
(although you would replace "*" with the list of columns, for readability :-p )
I think David's onto the right idea about initially populating the listbox. Add to the listbox after it's been created. It also means you should never need to edit the generated UI file :-)
MVC... Keep the data model separate from the User Interface.