Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
MmComboBox Issues
Message
From
19/08/2004 12:35:21
 
 
To
19/08/2004 11:56:22
General information
Forum:
ASP.NET
Category:
The Mere Mortals .NET Framework
Miscellaneous
Thread ID:
00934544
Message ID:
00934560
Views:
27
Joe

Couple of things. The most likely cause is that in order to trigger the automatic databinding event for an mmControl, the data source of the control has to change. Think of the sequence of events in the code that you posted. Your business object is instanciated, the mmComboBox is instanciated, and then the constructor ends. The data controls by your business object has not changed since the mmComboBox came into existance. Typically, what you'll have in your construtor is a block of code to instanciate your business objects, then the call to the InitializeComponent method, and then a block of code to populate your business objects with data (this will then trigger the databinding for the mmControls).

The seconds this is that although you say that the table managed by your business object has data in it, I'm not sure how that's possible since you've only instanciated it. I suppose the only way for that to be true would be if you have a call to a "populate" method in the objecs constructor. If so you might want to rethink that since you'll have to call that method again after the InitializeComponent call anyway.

Only final suggestion would be to verify that the BindingFlag property of the mmComboBox is set to TRUE. It should be by default but it's worth checking.

Hope this helps.

Scott
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform