Fernand Vanrie wrote:
Frank, are you telling that after opening a table and after we
scroll to the last record, (I suppose we have the content off the
table now in memory) the search go's back to the Server to find a
result ?? and the search is not using the resultset already present in
the memory off the local machine ?
BTW: filtering is done where ?
Hello Fernand,
Searching vs Filtering in Base is indeed quite different.
This moment is a very good time for me to review those differences,
purely for personal reasons (time has proven that I don't know nearly as
much as I once thought I did)-
Heres what I think:
Filters
- Change the result set contents
- - for rdb datasources this means a trip to/from the server
- filter criteria are automatically stored with dataview components
- setting filters is a purely modal action (no change to other UI
objects until the dialog is removed - or - the form data controls are
returned to display mode in the case of FilterByForm )
- - setting or removing filter criteria resets the record pointer within
the result set to the first record in the result set.
- - - when the result set is reset, upon setting or removing filter
criteria, only some number of records will be read to the client memory.
(the number will vary depending on the size of each row in the result set)
Searchs
- Applies search to current result set (there should not be any traffic
between the client and server -once- the current result set is read into
the clients memory)
- - for all datasources this means that the comparisons are performed on
the client machine
- - - so if you open a dataview for a table - a certain number of
records are retrieved - if you apply a search to this result set records
are retrieved from the server AS NEEDED as until the first match is
found of an in-memory row
- criteria is stored in a previously used queue
- the search dialog is not modal - but you can apply the search and see
the record found without clearing the dialog from the screen - can't
work with the calling form however until it is (is that really necessary?)
- - performing a search moves to the first matching record and changes
the current record pointer within the result set
- - - if no match is found the current record is not changed
But - there is more in the way of differences to be aware of, aren't there:
continued....
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
