>We are trying to find a way to speed up our APP at a clients site.
>
>Client:
>A mortgage banker. They have 30000 records in their master.dbf. They run from a server with 310Mg Ram, out through a gig card and through a gig backbone. They run switches and 100 cards at the client. The client machienes range from P166, PII233 up to PII400 all with 128Mg of ram.
>
>APP:
>A large VFP5 database for use with the mortgage banking industry. The program (in general) allows the user to track records on a loan basis. We have one main screen that you can bring up based on loan# which is a form with 8 tabs. We use classes though to help keep the load time down, and don't instantiate them until the tab is clicked. However when the form loads it seems to take a long time to bring back the data. This is where we are trying to cut speed. We were using direct references to the table, controlsource = master.field1. Then we changed over to a view and tried to use that to increase speed, but unfortunately it decreased speed.
>
>To summ it up I need to cut load time. My problem is that if I do a USE Master.dbf it will bring back the whole table. That's why I tried to use a view thinking it would only bring back the one record and thus speed up time. Like I said though the view only seemed to slow things down.
>
>I'm sure I forgot something you need to know, so let me know what else you need to give any thoughts. Thanks alot all!
>
>Shawn Burke

The first problem is bringing back the entire table. Using a view, you can cut this down. You should use a parameterized view that is optimized. See my web site for information on using Rushmore.