[AccessD] Combo box not displaying 6 numbers

[Stuart McLachlan]

My first thought:

Do  Cases have a status such as Open/Closed?  Do they need to see all previous cases or 
only Open ones?


On 10 Mar 2017 at 6:41, Rocky Smolin wrote:

> The combo box contains case numbers.  The form records calls from a
> call center and they are imported from other sources.  The case
> numbers are sequential starting at 10000. So if the user enter 1 I
> don't know yet where to trim. 12 and I can trim < 12000. 
> 
> R
> 
> -----Original Message-----
> From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf
> Of Jim Dettman Sent: Friday, March 10, 2017 5:17 AM To: 'Access
> Developers discussion and problem solving' Subject: Re: [AccessD]
> Combo box not displaying 6 numbers
> 
> 
>  That is always the inevitable question<g>
> 
>  But I think most end up here because that want the type ahead, which
>  you
> don't easily get with using something like a continuous form, and then
> you end up with a larger data set than you anticipated over time.  I
> actually see this quite often on Experts-Exchange and other places.
> 
>  If he wants to keep using the combo, then some type of filtering
>  needs to
> be done obviously.   Can be something like Bill suggested, using the
> technique that Allen showed, or possibly filter buttons (ie. a phone
> book list with 26 filter buttons, one for each letter).  
> 
>  You can use a continuous form and a text control to emulate a combo
>  BTW,
> it's just that you need to do the all the work for the lookup as you
> type functionality.
> 
>  Probably better off to filter in some way with a combo.
> 
>   One other suggestion on that; if the data set is based on dates at
>   all
> (ie. transaction), then I'll often filter with a "Back to" date and
> default it to one year.   That usually suffices to keep the data set
> relatively small and yet allows the user to go back further if they
> need to, which usually doesn't happen all that often.
> 
>   Not sure that would work here though because if they want to go back
>   to
> the beginning of time, then the combo's not going to handle it once
> again. Maybe a To/From date range and a message box when the combo
> overfills.
> 
> Jim. 
> 
> -----Original Message-----
> From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf
> Of Susan Harkins Sent: Friday, March 10, 2017 06:45 AM To: 'Access
> Developers discussion and problem solving' Subject: Re: [AccessD]
> Combo box not displaying 6 numbers
> 
> Rocky... I can't help but ask, why are you using combo? Is it really
> necessary to present this list in this way? 
> 
> Susan H. 
> 
> 
> Yes, that would be the work around.   Allen shows that here:
> 
> http://allenbrowne.com/ser-32.html
> 
> > Well that sucks :/ But probably explains it.  The last number is row
> > 65912 which is close enough.
> > 
> > I once had this situation and I had to write a routine with every
> > key press of the combo box to requery based on what had already been
> > entered.  That was back in Access 97.
> > 
> > Hope I don't have to do it on this one.  It was a PITA.
> > 
> > The limit on a combo's rows is 64K (65535).
> > 
> 
> 
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>