[AccessD] Has anyone ever sen a listbox not display all rows?

Max Wanadoo max.wanadoo at gmail.com
Fri Jul 31 03:33:32 CDT 2009


Actually...

1. You can tell it to avoid usys too if you wanted.  But...
2. I don't think this is the way to go as doing this increases bloat in
itself - ahem!

Better to write the list out to an ascii text file and then populate a combo
selection box from the contents.
That way, no bloat within the mdb and no msys/usys problems.

Max



-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan
Sent: 31 July 2009 02:20
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Has anyone ever sen a listbox not display all rows?

Doh!

Good thinking JC.

-- 
Stuart

On 30 Jul 2009 at 20:55, jwcolby wrote:

> Yes, I know that.  In this specific case eatbloat specifically avoids msys
tables but would export / 
> import usys tables.  I don't want these tables exported, thus I named them
msys.
> 
> It's a feature.  ;)
> 
> John W. Colby
> www.ColbyConsulting.com
> 
> 
> Stuart McLachlan wrote:
> > The convention is to leave msys tables to Access.  Use usys for your own
additional system 
> > tables.
> > 
> > On 30 Jul 2009 at 14:53, jwcolby wrote:
> > 
> >  source 2K string length limitation.  I created msys tables in my
library container and then populate 
> > 
> -- 
> 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




More information about the AccessD mailing list