Marcelo,
The search is done over all the table until get the number of records you want to display (in the sample 15, oGet:lenDisplay := 15, the common is 5), for that reason there is no scroll
But I wonder, did you intend to only show records containing the search term. For instance, now there are only 4 of the 15 records containing the search term (
pico). Also, it seems for large databases this is going to be very slow since every record in the database is going to have to be read and searched for each keystroke. It might be possible to create an index that doesn't contain the first item (address number in this case) which would be much faster. However, users would only be able to search on the second item (street name in this case).
I can see there are not interest in this control, if I have some time I will try to finish it, James, sorry for lost your time
I did not mean to imply that I was not interested. I am just trying to find out what you are hoping to accomplish and pointing out some of the issues with the current design. Users are only interested in getting the result they need as fast as possible.
I don't think time is lost pursuing any of these ideas. Without trying new things we don't learn anything new or develop anything new.
Please let is know of your progress.
James