Lookup Field Limit

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

We're designing a database which will hold details of 10,000 clients. We
intend to have several forms relating to our clients which we will complete
on a regular basis. I was just wondering would it be ok to use a lookup
field to select the clients when entering information?

I'm basically wondering was there a better way to do this as I thought some
10,000 clients would slow down data entry?

Does that make sense?
 
Ian,

Do not use the Lookup field feature; it has a number of problems--see the
following link for an explanation:

http://www.mvps.org/access/tencommandments.htm

However, if you mean using a combo box to present choices to the user, use a
"divide and conquer" strategy. At what point performance slows down enough
to be irritating to the user depends on a number of variables, but the
general idea is to present another combo box, or to use information from
another field to limit the choices in the combo box. This could be A-Z, or
by region, state, etc. After the narrowing selection has been chosen, use
the value in its AfterUpdate event (and the form's Current event) procedure
to reassign the RowSource of the 2nd combo box. Search the forum for
"Cascading Combo Boxes" for further information.

Hope that helps.
Sprinks
 
Back
Top