Hi Mel:

>I just had time to actually study this, and begin to implement my solution. However, after reading your reply's to John, I thought I would ask for a little clarification. I understand how CodeMine 7 requeries child views as mentioned above. In this situation, I have this one form that uses a non-parameterized view and no child records. I now have the view in a CDE. Is there a property setting I need to set in the CDE to do a requery, or would I implement a solution as you mentioned to me in the first reply to this thread?

Having a non-parameterized view largely negates the point of the view, unless of course that the view is very specific and you have been able to get away with a very specific SQL-Select statement in the view definition that only returns a sub-set of the data source. If your view matches your data source, there is probably little point in using a view in these circumstances. However, that is a design issue and your call.

To answer your question, normally, the lookup view is parameterized so that you can return the record or types of record(s) you wish to select from. When you select your record, the rest of the related views (in a CDE scenario) are re-queried automatically by the framework (assuming you have defined their relationships in the CDE). The lookup cursor that provides the search value could be a table - it doesn't have to be a view. The point I am making is the action that would generally initiate the requerying of the views (from a CDE perspective) is the looking up of your primary record to which all others are related.

In your circumstances, if you cannot find a logical point in the form's useage that cries out "requery me now", then you will have to put a requery type button on the form or toolbar. I don't know what the criteria is that dictates when a requery would be required, other than the fact that the user just feels like requerying the form. I would find it hard to believe that there isn't a predictable point that a requery should occur. If there is, you could dispense with the button and just requery the view when the appropriate event occurs in the life cycle of the form.

HTH

Best