Denis:

What you are trying to do is essentially call the cursor class's requery method. Obviously, you can call the requery method from anywhere you like; from the form via the datamanager or from within the CDE itself.

However, there is generally no need to manually requery a parameterised view as this is handled by Codemine automatically.

If you go into the builder for a cursor object and look at the RI (referential integrity) section, you can tick the box that say's "automatically requery cursor when parent moves" (or words to that effect). So, as long as you have set the relational parameters correctly for the cursor (again in the builder) ie., specified the primary and foreign key fields for the cursor, the requerying is, for all intent and purposes, automatically handled for you by the framework.

When the cursor is based on a parameterised view, Codemine automatically assigns the parent value (as specified by you in the cursor properties) to the view's parameter variable (as specified in the view definition). If the cursor is a table it uses native SET RELATION TO or SET KEY TO logic. So, irrespective of the cursor type, as long as you specify the primary/foreign key field values (and set the cursor's order where appropriate), you don't have to worry about requerying a parameterised view.

HTH

-=Gary


>CodeMine 7.0 RC2
>
>In the CDE what would be the best place to requery a parameterized view?
>
>I want to get all the record so the CDE should be the best place to do this
>requery.
>
>It not the CDE would it be better in cmRule or cmCursor?