Number of values in a combobox

  • Thread starter Thread starter BK
  • Start date Start date
B

BK

I have a bit of a problem. I have a drop down where I need to have ALOT
of values. We're talking over 10000. Yes, yes I know this is bad
design. The person I'm designing this for wants it this way. Basically
the db tracks all our jobs. I have a combobox at the top of the form
that lets them go to a specified record. The thing is we have what is
called a standing job in some cases. The job number is the the same but
we append a numeric identifier after it, simply in order. So if the
last time we worked that job the jobnumber was 123456-10, then next time
it would be 123456-11. But when they need to add a new record they go
to the combobox and look up the value of the last one (by typing in the
standing jobnumber and then scrolling to see the last one). Then they
add a new record and append the jobnumber with the appropriate number.
Right now we have 13000 job numbers so a lot of these don't show up
since I think there is a 10000 record limit on it. Is there a way to
disable that? Or if anyone has a better way of approaching this, since
it is not exactly the best solution I'm amenable to that (however the
person I'm designing this for may not be *grin*). Although the speed of
the form with all those values is VERY fast, so performance is not an
issue with it at all. The only requirement would be that it stays on
the same form and be fairly small in size. I'm working in an adp with
SQL Server 2000.

TIA,
Bill
 
BK said:
I have a bit of a problem. I have a drop down where I need to have ALOT
of values. We're talking over 10000. Yes, yes I know this is bad
design. The person I'm designing this for wants it this way. Basically
the db tracks all our jobs. I have a combobox at the top of the form
that lets them go to a specified record. The thing is we have what is
called a standing job in some cases. The job number is the the same but
we append a numeric identifier after it, simply in order. So if the
last time we worked that job the jobnumber was 123456-10, then next time
it would be 123456-11. But when they need to add a new record they go
to the combobox and look up the value of the last one (by typing in the
standing jobnumber and then scrolling to see the last one). Then they
add a new record and append the jobnumber with the appropriate number.
Right now we have 13000 job numbers so a lot of these don't show up
since I think there is a 10000 record limit on it. Is there a way to
disable that? Or if anyone has a better way of approaching this, since
it is not exactly the best solution I'm amenable to that (however the
person I'm designing this for may not be *grin*). Although the speed of
the form with all those values is VERY fast, so performance is not an
issue with it at all. The only requirement would be that it stays on
the same form and be fairly small in size. I'm working in an adp with
SQL Server 2000.

TIA,
Bill
Click to expand...
 
If you held two fields, one for the job number, and a separate field for the
series number, you could do this much easier, with a subform to show the job
number list, and a combo box just to show the series numbers. Of course you
could still concatenate the two fields together for display purposes in a
query, just to preserve your existing display ( if that is necessary ).

--
Regards,

Adrian Jansen
J & K MicroSystems
Microcomputer solutions for industrial control
 
Back
Top