Hi Elgin,

Unless there is a real compelling need not to do so, I'd stick the views in the DataEnvironment and be done with it. You might want to set NoDataOnLoad to .T. and do a REQUERY() on the applicable view only when that page is clicked on, though, to speed things up a bit.

Now if the views are parameterized on CUSTID and UPSINO, then when the user enters a new value for these, you can just requery the views for current open pages.



>I have a form that has a PageFrame with 7 pages each with a grid. The dataenvironment for this form consists of 7 views, with each view made up of a single table with the exception of Nameplatv which is made up of Nameplat and Cust tables. Some of the views are : Nameplatv(parent), Dgav(child), Icpv(child), Liquidv(child), etc. In my 7 pages with grids, I want to display records from a single search for each of the grids and their respective views. The search criteria will be CUSTID and UPSINO (which stands for upsi number). Both of these criteria exist in all views and tables. Some searches may be by CUSTID only. Questions:
>
>1)When and where is the best place to Load the dataenvironment? Do I let all tables and views (total 15 work areas) load on the form's "Load" event. Or do I load views only when used and if so where? For example the user may never even view the ICPV tab during any one session, but when they click on that tab I want the data to be there Fast.
>
>2)Or should I re-think my whole dataenviroment and make only two views (1) NAMEPLATV and (2) AllChildTables, thereby having only two views for the whole dataenvironment?
>
>My goal is to enable the user to lookup a single or group of records then double click on any one record in a grid and display another form containing the details of that record.
>
>Thanks for the suggestions and help
>
>Elgin Rogers Jr
>Epic Solutions