List Box length is limited?

  • Thread starter Thread starter Jonathan Scott via AccessMonster.com
  • Start date Start date
J

Jonathan Scott via AccessMonster.com

In Access97, I am finding that a List Box has a limit of 2048 characters
assignable to it. Are there any suggestions on how to get around this? I have
a sequence of "commands" that the user defines, which could be of variable
length, and breaking these up into multiple List Boxes is out of the question.


Any suggestions would be great!

Jonathan Scott
 
Hi Jonathan,

The only way round this that I know is to store the "commands" in a
table and use a query on the table as the RowSource of the listbox.
 
I found the following link on a callback function, but I am unsure how to use
it.

http://www.mvps.org/access/forms/frm0049.htm

Has anyone else used this? Is there any hope of being able to have my listbox
and transactions? If only there was a way to specify database connection when
issuing Control.Requery!

Jonathan Scott
 
Changes to the list are happening inside of a transaction, and I need to be
able to refresh the list, inside of that transaction. I don't see how I can
tell the RowSource to use my connection which has the transaction started.

Perhaps I will have to forgo the pleasure of having a transaction. Hopefully
this kind of stuff is "fixed" in Office 2003.

Jonathan Scott


John said:
Hi Jonathan,

The only way round this that I know is to store the "commands" in a
table and use a query on the table as the RowSource of the listbox.
In Access97, I am finding that a List Box has a limit of 2048 characters
assignable to it. Are there any suggestions on how to get around this? I have
Click to expand...
[quoted text clipped - 4 lines]
Jonathan Scott
Click to expand...
Click to expand...
 
Access 2003 does seem to allow longer value lists.

My instincts say it's a bad idea to be modifying the user interface
within a transaction, but I don't have any particular experience to base
this on.

Changes to the list are happening inside of a transaction, and I need to be
able to refresh the list, inside of that transaction. I don't see how I can
tell the RowSource to use my connection which has the transaction started.

Perhaps I will have to forgo the pleasure of having a transaction. Hopefully
this kind of stuff is "fixed" in Office 2003.

Jonathan Scott


John said:
Hi Jonathan,

The only way round this that I know is to store the "commands" in a
table and use a query on the table as the RowSource of the listbox.
In Access97, I am finding that a List Box has a limit of 2048 characters
assignable to it. Are there any suggestions on how to get around this? I have
Click to expand...
[quoted text clipped - 4 lines]
Jonathan Scott
Click to expand...
Click to expand...
Click to expand...
 
Back
Top