Re: FORMS Query Array Size

>I have a FORMS app that returns about 200 rows for an average query. It
>only retrieves a single row at a time. I am trying to increase the
>arraysize so that I can retrieve 50 rows at a time. According to the
>documentation, I can set the 'Query Array Size' property to do just
>that. However, after setting it, I failed to notice any difference.
>When every record is stepped through, the status bar indicates that the
>system is "working...". There is also a very slight hesitation. There
>was absolutely no noticable difference in performance. I can only
>conclude that this variable had no effect. I ran a subsequent query
>that only retrieved 15 rows. I expected all of them to come back at
>once, but again, the system appears to be getting them one at a time.
>Is there any other variable that I must set? 'Query All Records' isn't
>an option. A fat finger could inadvertantly cause many thousands of
>rows to be dragged across the LAN. Does anyone have any experience with
>this?

Oracle returns a number of rows based on what is displayed on the screen; something like (# displayed + 3). I really haven't seen the 'Array Size' work either. The hesitation is perhaps due to any processing (post-query, when-new-record-instance, when-new-item etc triggers). If you form has lots of items, you might have a problem with not enough video memory. Set the cursor in the post-query, and see how long it takes from when the cursor changes to when you see the row get painted. If there is a delay, you need more/faster video, or fewer items.

Dan Hekimian-Williams Received on Tue Sep 01 1998 - 07:19:17 CEST