Hi Tester,
Based on my understanding, you want to give certain initialize order rule
for your component.
Actually, it is not recommanded for you to develop a custom control has the
strong dependency on another control. Your logic may have this dependency,
but you should not apply this dependency at design-time. For example, if
DataGrid does not bind to a dataset, it can not do anything(We first does
not talk about other datasource). But if we drag a datagrid on to the
designer, we still allow it to be created.
Usually, I think ISupportInitialize interface may meet your need, use it,
you can determine if certain property of this component is set, then you
can signal the initialize complete in ISupportInitialize.EndInit(), for
more information, please refer to:
http://www.howtodothings.com/showarticle.asp?article=581
Thank you for your patience and cooperation. If you have any questions or
concerns, please feel free to post it in the group. I am standing by to be
of assistance.
Best regards,
Jeffrey Tan
Microsoft Online Partner Support

Signature
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Hi Tester,
Does my reply make sense to you? Do you still have concern on this issue?
Please feel free to feedback. Thanks
Best regards,
Jeffrey Tan
Microsoft Online Partner Support

Signature
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Tester - 28 May 2004 03:46 GMT
Hi Jeffrey,
Thank you for posting a reply.
For some reason I thought databinding took place when .DataSource was
assigned. For example,
dataGrid1.DataSource = someData;
But it's not. Data binding happens after InitializeComponent completes. It
seems to work fine now. If i hit the non working case, I'll post again.
Thank you
> Hi Tester,
>
[quoted text clipped - 7 lines]
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.