Hi Dennis,
well, I can't tell you about FetchAsNeeded as we don't use that feature. We are using FetchSize which reads 200 records via ODBC and as soon as the user reaches the end of that block, the next 200 record will be fetched.
I assume that FetchAsNeeded does exactly what you expect it to do.
BTW, we don't use filtering in those grids that use this property. So, I can't tell you, if filtering would interfer in some way
>Thomas,
>
>Thanks for your reply. I am using CAs.
>
>Do you mean to say using FetchAsNeeded or FetchSize will automatically regulate how many rows the CA will ask from the database server?
>
>To explain further, let us say my data entry form class has a grid which initially has a viewable area of 20 rows, then the CA will automatically fetch 20 rows? Then, when user maximizes that form (hence making the grid bigger) it will automatically adjust fetching the appropriate number of rows?
>
>Dennis
>
>
>
>
>>Hi Dennis
>>
>>you could use CURSORSETPROP properties like
>>
>>FetchAsNeeded
>>or
>>FetchSize
>>
>>If you are working with CA then there are equivalent properties available.
>>
>>
>>
>>>Hi Experts,
>>>
>>>I have a data entry form class that has a pageframe control with two pages, one showing a grid, the other showing current record contents of the "active record".
>>>
>>>This is just fine if I use DBFs as backend data, since it is mere file sharing. This does not augur well though if the same data entry form class is used since ALL rows from a MySQL server database will be fetched (which may run into 100s of thousands)
>>>
>>>My question is - what is the best practice for a Client-server data entry form:
>>>1. Get first X number of rows?
>>>2. Show no data at first then have a "new function" to view (in addtion to Edit, New, Delete) with certain filter conditions?
>>>3. I am leaning towards how Yahoo Mail UI does it - but how would you implement the "coordination" of fetching the right number of rows
>>> when user resizes the message header pane?
>>>
>>>Thanks In Advance
>>>Dennis
Best Regards
-Tom
Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it.
Oh, and BTW: 010101100100011001010000011110000101001001101111011000110110101101110011