Dropdown Memory Issue

  • Thread starter Thread starter ChristineS
  • Start date Start date
C

ChristineS

I have a client that enters so many records and I have a dropdown query that
takes them to the record selected. The problem is that there is so many
records that the record they are seeking does not appear on the drop down
list. I have reset the rowsource after they start typing but this seems to
cause some time delay that they are complaining about. Is there any way to
increase the number of records a dropdown list will display???

Thanks,
 
The fact that there are so many records in a drop down tells it all. The
question is does the dropdown keeps it functionality used this way. Anyway
you could change the rowsource by getting a required number of records for
instance show first 500 and put a button which when clicked shows next 500.
Put a hidden textbox on the form to keep track how many times the button is
clicked. That way you can determine which set of records has to be fetched.

just a suggestion...
 
Thanks Maurice for the response. Actually it has worked quite well so far.
Unfortunately my clients are very spoiled and want to be able to continue in
the way they worked before. As I stated I was already limiting the records
based on the first two characters they entered into the box but even the
slight hesitation created by reselecting the rowsource query seems to bother
them. Again thanks.
 
Christine,

If you have a combo box that contains that many records, you probably need
to implement some other filtering functionality, or consider moving your
backend data to SQL Server, then you can perform some of the filtering on the
server.

With Access, no matter how you filter the recordset for the combo box, the
processing is all done on your local computer, so Access has to bring the
entire recordset across your network and then filter it for the combo box.

How many columns are you returning for your combo box? You might be able to
speed things up by limiting the number of columns. You might also be able to
speed things up by creating an index on whatever field you are filtering by
in your combo boxes Change event (I assume that is where you are doing your
filtering based on the first two characters entered).

With a SQL Server backend, you can use passthru queries that run on the
server, and therefore only return a subset of the records across your
network, speeding up your application.

Dale
 
Back
Top