Get the query from the user, then send that back and only retrieve the records that match.


>I know that probably this question has been asked before but i haven't been able to get the answer i have been looking for.
>
>let me explain you guys in detail the scenario:
>
>1. I have a table PREmployees,
>2. The employees for this customer are about 2,000 people
>3. The application was requested to store an historic of every week, so it is 2,000 records per week, so more than 100K records a year
>4. I am using a CursorAdapter parametrized for bringing only the records for an specific week
>5. when the screen opens , the Cursorfill fires and brings 2,000 records for the specified week
>6. The user can change the week as discretion so all years, all weeks must remain on the table
>7. On the screen there is an option to display a search window
>8. i am using odbc with a shard connection handler
>
>the problem:
>when i run the screen on the server takes a couple of seconds, but when the users runs it on their desktop through the network, takes a little more, probably a minute or so
>
>what i am looking for:
>1. an idea on how to reduce the time consuming for the user when opening the screen
>2. understand if fetchasneeded might help with out affecting my search window cause in order to search uses the Cursoradapter resultset, all 2000 records
>3. for me 500K records is not that much, but is taking to long to retrieve, i might be doing something wrong?
>
>what i am not looking for
>1. ideas on how to split table. not interested in this
>2. stop using CA, not an option, my whle system is bases on this
>
>tnx in advance