It seems we have lost a lot of functionality and ease with Combos and Listboxes.
Looking at the List of Properties, Methods and Events we used to have in VB6 and is no longer supported in VB.Net, I was rather sad. These PMEs have not been replaced with something equivalent to make it easy.
What are the BASIC uses for Listboxes/Combos ANY developer should be able to do?
1) Populate the control with Data from some lookup table in a DB
2) Set the initial value held in the control to -1 so it is blank to begin with
3) Let the users select a value/listed choice in the List
4) Store that selected value in a DB Table.
5) Retrieve the stored value again at a later point
THIS IS what 3rd Party Control vendors andeven Microsoft keep in mind when creating controls. If one cannot do any of the above/all of the above the control is a waste of time and should not be used.
I wish they would LISTEN to us!
In the Controls collection of VB6 we used to have the ItemData property which we used to store the ID Value of the LookupTable in. Now we do not have it anymore.
So they try and tell you that yes, their control still works and is even better, just bind it to the Dataset! Set the DisplayMember and the Valuemember, then retrieve it again with the SelectedValue Property or the SelectedIndex Property. But then you cannot set the SelectedIndex to -1, which gives your users a nice blank combo to start with!
You cannot set the myCombo.Text = "" property either! So back to the beginning and in the end we all, like suckers settle for a measly second best.
sorry Microsoft, give us back the properties we had in the Combos! Your controls are not worth much without it!
Anyone else struggling with Itemdatas and some missing PMEs?
Let us know!
Maybe someone an help us with some REAL solutions!
Rgds
Len
Quiet as a bulldozer Mate!
Looking at the List of Properties, Methods and Events we used to have in VB6 and is no longer supported in VB.Net, I was rather sad. These PMEs have not been replaced with something equivalent to make it easy.
What are the BASIC uses for Listboxes/Combos ANY developer should be able to do?
1) Populate the control with Data from some lookup table in a DB
2) Set the initial value held in the control to -1 so it is blank to begin with
3) Let the users select a value/listed choice in the List
4) Store that selected value in a DB Table.
5) Retrieve the stored value again at a later point
THIS IS what 3rd Party Control vendors andeven Microsoft keep in mind when creating controls. If one cannot do any of the above/all of the above the control is a waste of time and should not be used.
I wish they would LISTEN to us!
In the Controls collection of VB6 we used to have the ItemData property which we used to store the ID Value of the LookupTable in. Now we do not have it anymore.
So they try and tell you that yes, their control still works and is even better, just bind it to the Dataset! Set the DisplayMember and the Valuemember, then retrieve it again with the SelectedValue Property or the SelectedIndex Property. But then you cannot set the SelectedIndex to -1, which gives your users a nice blank combo to start with!
You cannot set the myCombo.Text = "" property either! So back to the beginning and in the end we all, like suckers settle for a measly second best.
sorry Microsoft, give us back the properties we had in the Combos! Your controls are not worth much without it!
Anyone else struggling with Itemdatas and some missing PMEs?
Let us know!
Maybe someone an help us with some REAL solutions!
Rgds
Len
Quiet as a bulldozer Mate!