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

Yep.  It just occurred to me that since it is now a common library, it is technically possible to 
have collisions like this.

John W. Colby
www.ColbyConsulting.com


Max Wanadoo wrote:
> FWIW I thing multi-user is not a requirement.  It should only be run by a
> competent person, ie the develop for specific purposes and as it runs
> "UNDER" the project "root" folder and is "date specific" it should never
> conflict with anything else.  What you could do is perhaps put a flag up to
> say it is "In progress" and stop another invocation starting.
> 
> Ma
> 
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
> Sent: 30 July 2009 19:53
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Has anyone ever sen a listbox not display all rows?
> 
>  > Why didn't I think of that....
> 
> Speaking of which, I got Eatbloat (my version) populating tables to get
> around the list control data 
> source 2K string length limitation.  I created msys tables in my library
> container and then populate 
> those tables instead of building up a huge comma delimited string for the
> list control data source. 
>   Now the table can hold as many objects as needed and the lists use the
> tables as their data source.
> 
> It just occurred to me that I may need to add "multi-user" handling because
> my version can 
> theoretically be used in many different FEs at the same time.  I'll probably
> need to track which FE 
> the objects are coming from, something like that.
> 
> Anyway, it works great so far.
> 
> John W. Colby
> www.ColbyConsulting.com