Kevin,

>The point here is that the navigation business object's Navigating/Navigated events are raised. In the next object down the hierarchy, you have code in your hook methods that responds to this event. If you have nothing in that hook, the buck stops there. However, if you have code in the hook that calls that business object's NavigateData() method, the next object downstream would receive those events, and its hook methods would fire. Given your scenario, it sounds more like you want to put code that retreives data in the hook...in that case, the next object downstream would receive Retreiving/Retrieved events to which you can respond.
>
>Regards,

Kevin,

I realize that this matter has taken up a lot of your time. I thank you very much for that. Perhaps my none-native nature of English prevents me to be understood, and to understand your points. Since I am very new with .NET development, I basically can only do development work following the Jump Start tutorial application model and all my business objects are modeled after the business objects in the Jump Start.

I can now narrow down what I want to know into two questions:
1. Am I correct in stating that on a form at most only one grid can be navigated and the business object bound to that grid is the only one business object that raises navigating/navigated events caused by record pointer movement in the grid?
2. If I am correct for question one, for the rest of grids on the form, when the record pointer is moved, what events do their bound business object raises?


Regards,

Chen