Combo Lookup Field

[Guest]

Hi,

We've got a database where clients place orders. On the orderform we use a
combo box which looks up the client table. We now have several thousand
clients and I would like to improve this system.

Is there a standard way of doing this?? If not what is the best solution??

Hope somebody can suggest something, many thanks

Ian

 

[Guest]

Here is a site that may help:
http://allenbrowne.com/ser-32.html

 

[Jeff Boyce]

Ian

Define "improve"...

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Jeff Boyce]

Ian

.... or to put it another way, ...

If you don't tell us what you think is wrong with it, we can only guess what
it might take to "fix" it...

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Guest]

I assumed that our current method was fundamentally wrong, having a combo box
lookup field with thousands of rows and was basically wondering how other
people do in this situation.

I dont really know what I was expecting in response. What would you do in
this situation??

 

[Jeff Boyce]

Ian

If the users aren't complaining (if they were, probably about slow
performance), and if my sense of right/wrong weren't offended, I wouldn't
touch it ... it's working!

If the users WERE complaining, it probably would be about slow performance,
and it probably would offend ..., so I'd use the link Dave provided in
another response to speed up the performance.

Another thought... how many fields are being returned in the query that
feeds the combobox? If its more than 2 or 3, it may be too many. I'd first
try reducing the number of fields returned, then I'd look at the underlying
table(s) to make sure they were indexed appropriately, then (if still slow
performance), look to Allen's approach.

Regards

Jeff Boyce
Microsoft Office/Access MVP