Basing the parameterized view to a key in the parent isn't a good idea for reasons you're running into now. Instead, base it on a variable, and when you need to requery the view, change the value of the variable to match the key of the parent. Also, this way you can open the view without the parent by just initializing the variable.

>I've got a form using a parameterized local view to fill a grid. My local view is parameterized, based on a key value from the parent table. In the VFP design environmet everything works great. However, when I compile, and run, either as an app or an exe, the form loads, and then hangs just as the Data Environment attempts to initialize.
>
>The view is in the data environment, and was added after the parent table, if that makes any difference.
>
>I'm thinking this may be an issue with the parameterized view.... If I open this manually, I need to have the parent table already open before the view is opened, otherwise, it attempts to ask for a key for the parameter. Is there some way to guarantee the order in which things open in the data envinronment?
>
>I added code to the error method of each table in the data environment, and the error is triggered when the DE attempts to open the view.
>
>TIA for any ideas.
>
>--- Larry