How should I handle this situation ? What is the best practice ?

I don't understand your code, but it sounds like you just need to create a shared property (or dictionary) to test against so that your Init logic doesn't fire more than once.

Do you compare BBS and native binding source component / DataTable binding? Does BBS work well ? Is there a performance issues ?

The performance should not be an issue whatsoever.  This is something that is commonly done (including ourselves).  The BBS i something that continues to grow and is what we use exclusively for reporting and grids.  So you wil be in good shape

After query, I've deleted the business object from the dictionary. BBS starts to ctruct the business object list. Since I've deleted the object from the dictionary, I Couldn't test the condition and my init logic runs many times.

Could I get your solution ? "Shared property or dictionary based solution".

Firstly, Constructor fires for the business object itself. After BBS starts and fired many times the same constructor ? How can I understand from where constructor is called ? (i.e BBS calls the constrctor ?) 

1) Add a shared (static) boolean property to your base business object called "InitFired" or some such which will be defaulted to False

2) In the init of your base business object, all logic should go inside of an If Test ("If Not InitFired Then ...").

3) Inside of that if test, you should set the InitFired property to True. That way, any subsequent firings of the init on the business objects will be negated (it will test on the initfired property, see that it is true, and skip all of the logic within)

The source of the problem is likely in that a new instance of the business object is created for each row in the grid. As such, each row is currently firing the init method for the business object. Using the above, any undesired inits should be bypassed. Keep in mind that you will need to reset the shared InitFired property yourself whenever appropriate (i.e. once the grid is fully populated).

Hope it helps

Dustin

I couldn't catch the end of the action (i.e Grid populated fully or BBS translates last row)

Firstly, I want to solve this case in the base (Say Our Custom framework)

I don't want to write any code to catch the action in our forms.

Thanks for the response.

I think this must be solved on the framework. A Shared property can be used to set to when calling "Activator.CreateInstance" and reset after the operation. Developers check this property to manage the flow. This  was the most convienent method that I've found.

Thanks.