Slow Retrieval in Forms Multi-Block
Date: Fri, 11 Dec 1998 20:55:22 -0500
Message-ID: <3671CD09.661E60E0_at_mindspring.com>
[Quoted] [Quoted] I have a multi-block Form that contains relationships from the primary [Quoted] block to four other blocks. In addition, there are three data elements in the primary block that are pointers to a reference table. I use a POST-QUERY trigger to populate non-database fields with the actual values from the reference table, so that the display has more meaning to the users.
I don't use a view because I need control of the INSERT/UPDATE/DELETE processes. When the users run a query, the first rows come back very quickly (1-5 seconds) depending on selection criteria. However, the users wanted a way to quickly traverse to the last record in the result. I therefore provided a button that executes the LAST_RECORD built-in. When the result set is of moderate size, 300-800 records, it takes upward of 90 seconds to retrive all of the records. Once cached on the client, they can instantly travers back and forth. But the wait up front is unacceptable. I have played with settings for 'QUERY ARRAY SIZE' and 'NUMBER OF RECORDS BUFFERED' without any improvement. I've heard that PRE-QUERY & POST-QUERY triggers are slow, but this is ridiculous. I am using array-processing, and it slows down even further when I turn it off, so I know the array processing is having a positive affect, just not enough.
[Quoted] Do I have a design flaw? Is there a better way to display a primary table, 5 related tables, and a reference table more efficiently? I don't want to have to use of view because of the update headaches? Any suggestions????????
Ed Jennings
-- ~~~~~~~~~~~~~~~~~~~~~~~~~ jenningse_at_mindspring.comReceived on Sat Dec 12 1998 - 02:55:22 CET