I am writing an app in VB5.
Part of my UI design calls for an array of Combo boxes (normal or DBCombo, I'm not fussed) that will have as the list, the contents of a field in an access db.
What I am currently doing, is to have a Data Control linked to the table, called datMaterials.
No I can only place the first combobox at design time, and this is called cmbMaterial(0).
A subroutine then determines (according to other factors) how many controls are needed and loads them. The problem I am having though, is that even though the ListField, RowField properties etc... are inherited by the newly loaded controls, the lists are always empty, so that only cmbMaterials(0) has a populated list.
Does anyone have any ideas, remembering that the lists have to be updatable if the user chooses to add a new definition, through a seperate process.
Part of my UI design calls for an array of Combo boxes (normal or DBCombo, I'm not fussed) that will have as the list, the contents of a field in an access db.
What I am currently doing, is to have a Data Control linked to the table, called datMaterials.
No I can only place the first combobox at design time, and this is called cmbMaterial(0).
A subroutine then determines (according to other factors) how many controls are needed and loads them. The problem I am having though, is that even though the ListField, RowField properties etc... are inherited by the newly loaded controls, the lists are always empty, so that only cmbMaterials(0) has a populated list.
Does anyone have any ideas, remembering that the lists have to be updatable if the user chooses to add a new definition, through a seperate process.