>>>I currently have a form with a pageframe with multiple pages. Each page contains a grid from a different related file. The user views one account at a time, with each page showing the related information for that account (i.e. - one page shows addresses, another phones, etc.) This form takes a very long time to load and I want to know how I can speed it up. Right now I have all of the tables in the data environment of the form with relations set up in the data environment. As the user navigates between accounts, the grids refresh with the related information. Is there a better way of handling the data? Would it be faster to use (parameterized?) views? How can I make the form load faster? Any suggestions greatly appreciated!
>>>
>>>Thanks,
>>>Elyse
>>
>>I am setting the same thing up with a Configuration Management System I am designing. I have several related tables set up in the data environment. I use parent child relationships throughout. One page tab will be the parent grid that the user can scroll down through to get to the item he/she wants, then another page tab will contain a child grid. I have a refresh() on each tab to ensure that the user will be looking at the relationship correctly. As far a slowness I dont see any, in the init I ensure that the tables are positioned at the top and let VFP handle moving the child tables for me. I tried viewes but they were not flexible enough, but I have not given up on them yet.
>
>How large are your files? I've noticed that the larger my files are, the slower the form loads.


Try setting AutoOpenTables to False in the Dataenvironment. Then in the init of the form you could programmatically open just the table on the first pageframe, with something like a timer to open the child tables later. This is somewhat of a kludge, though. However, Autoopentables to false will load the form faster

Also, if all your controlsources are all in grids, you can use the linkmaster, childorder and relationalexpr properties to tie the grids together without having to join the tables explicitly in the DE. I don't know if there are any performance benefits, but other users here recommend it over joins in the DE.