>I don't quite understand what you are referring to here, as I never used CodeMine prior to v.7.

The view handling wasn't as good in CM6 as it is in CM7. In 6, a view was pretty much thought as something you re-queried interactively from say the toolbar using the button you have mentioned in this thread. To re-query the view, you needed values for the view parameters so, you clicked the requery button on the toolbar (or form) that called the requery dialog, that established the values from the user and subsequently requeried the view(s).

This is OK if you want to find a particular record and you have a value on which to query. This type of approach borrows from Codebook. However, in CM7, a view is just like any other cursor and in the CDE, you set the PK/FK as properties of the view cursor object and then Codemine automatically requeries all views as and when required. So, whilst there is still a place for the requery dialog, you are more likely to have a field(s) on your parent form to type in your query/lookup value(s), and then hit a command button that issues a requery call passing the value(s) in the form field(s) as the requery parameters to the primary view. Then, as the view populates and you move the pointer in the parent view, Codemine will automatically requery all of the related views in the CDE where the cursor's lRequeryWhenParentMoves property is set True.

HTH