G
GillesRégis
I want to know if there is a way to use more than 65565 items/lines in a
listbox or a combobox in Access
listbox or a combobox in Access
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
D
Dirk Goldgar
GillesRégis said:I want to know if there is a way to use more than 65565 items/lines
in a listbox or a combobox in Access
No. It would be a very cumbersome user-interface design, anyway.
Better would be to provide some mechanism to restrict the number of rows
listed to a more workable number.
J
John Welch
You shouldn't even be trying to do that. There will be much better ways to
do whatever you are trying to do.
do whatever you are trying to do.
A
Albert D.Kallal
That is a lot of data...and usually too much for a user....
You can use a continuous form, as they can look like a listbox anyway.
There is some screen shots of this here:
http://www.members.shaw.ca/AlbertKallal/Articles/Grid.htm
however, while the above shows how continues forms (which don't have a
limit) can be used, what is more usually about those screen shots is how the
number of records is LIMITED. You can well note how several of those forms
"prompt" the user for what they are looking for. This is a much better
approach then loading huge numbers of records that the user don't need...
Here some ideas on this concept:
http://www.members.shaw.ca/AlbertKallal/Search/index.html
You can use a continuous form, as they can look like a listbox anyway.
There is some screen shots of this here:
http://www.members.shaw.ca/AlbertKallal/Articles/Grid.htm
however, while the above shows how continues forms (which don't have a
limit) can be used, what is more usually about those screen shots is how the
number of records is LIMITED. You can well note how several of those forms
"prompt" the user for what they are looking for. This is a much better
approach then loading huge numbers of records that the user don't need...
Here some ideas on this concept:
http://www.members.shaw.ca/AlbertKallal/Search/index.html
T
TC
Even if you could - you shouldn't!
As the others have said: why do you want that many items? What are you
actually listing in there?
HTH,
TC
As the others have said: why do you want that many items? What are you
actually listing in there?
HTH,
TC
T
Tom Wickerath
Hi Gilles,
As others have already mentioned, way too many records to have in a combo or
list box. Try the suggestion shown under the heading "Combo and list box
controls" in this article:
http://msdn.microsoft.com/library/d.../en-us/dnacbk02/html/ODC_CookbookChapter8.asp
Tom
http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________
:
I want to know if there is a way to use more than 65565 items/lines in a
listbox or a combobox in Access
As others have already mentioned, way too many records to have in a combo or
list box. Try the suggestion shown under the heading "Combo and list box
controls" in this article:
http://msdn.microsoft.com/library/d.../en-us/dnacbk02/html/ODC_CookbookChapter8.asp
Tom
http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________
:
I want to know if there is a way to use more than 65565 items/lines in a
listbox or a combobox in Access
G
GillesRégis
Thank you for your answer.
My application is a dictionary, it's why I have so many lines. I need to be
able to browse through the listboxes of my application, so I'm not sure I can
load repeatedly a subset of records. Moreover, I have a lot of lists
containing diferent items (French word, Icelandic word, etymology, and so on,
and each of these lists is used in several parts of my application to help me
input data in textboxes (traduction or ethymology of a word for instance).
This is possible throuh a dichotomous algorithm that is very fast, even with
64 000 lines per list ... unless I have to load repeatedly a subset of those
lines. I will first study better your ideas, and next I will see.
Bye.
My application is a dictionary, it's why I have so many lines. I need to be
able to browse through the listboxes of my application, so I'm not sure I can
load repeatedly a subset of records. Moreover, I have a lot of lists
containing diferent items (French word, Icelandic word, etymology, and so on,
and each of these lists is used in several parts of my application to help me
input data in textboxes (traduction or ethymology of a word for instance).
This is possible throuh a dichotomous algorithm that is very fast, even with
64 000 lines per list ... unless I have to load repeatedly a subset of those
lines. I will first study better your ideas, and next I will see.
Bye.
T
Tom Wickerath
Hi Gilles,
I'm not sure what a dichotomous algorithm really means. The performance may
be quite acceptable if everything is on the local hard drive of a PC.
However, as soon as a network is involved (for example, a split multiuser
database, with the BE on a file server), the performance might be painfully
slow.
Tom
http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________
:
Thank you for your answer.
My application is a dictionary, it's why I have so many lines. I need to be
able to browse through the listboxes of my application, so I'm not sure I can
load repeatedly a subset of records. Moreover, I have a lot of lists
containing diferent items (French word, Icelandic word, etymology, and so on,
and each of these lists is used in several parts of my application to help me
input data in textboxes (traduction or ethymology of a word for instance).
This is possible throuh a dichotomous algorithm that is very fast, even with
64 000 lines per list ... unless I have to load repeatedly a subset of those
lines. I will first study better your ideas, and next I will see.
Bye.
This is possible throuh a dichotomous algorithm that is very fast, even with
64 000 lines per list ...
I'm not sure what a dichotomous algorithm really means. The performance may
be quite acceptable if everything is on the local hard drive of a PC.
However, as soon as a network is involved (for example, a split multiuser
database, with the BE on a file server), the performance might be painfully
slow.
Tom
http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________
:
Thank you for your answer.
My application is a dictionary, it's why I have so many lines. I need to be
able to browse through the listboxes of my application, so I'm not sure I can
load repeatedly a subset of records. Moreover, I have a lot of lists
containing diferent items (French word, Icelandic word, etymology, and so on,
and each of these lists is used in several parts of my application to help me
input data in textboxes (traduction or ethymology of a word for instance).
This is possible throuh a dichotomous algorithm that is very fast, even with
64 000 lines per list ... unless I have to load repeatedly a subset of those
lines. I will first study better your ideas, and next I will see.
Bye.
G
GillesRégis
Thank you for your answer.
My application is a dictionary, it's why I have so many lines. I need to be
able to browse through the listboxes of my application, so I'm not sure I can
load repeatedly a subset of records. Moreover, I have a lot of lists
containing diferent items (French word, Icelandic word, etymology, and so on,
and each of these lists is used in several parts of my application to help me
input data in textboxes (traduction or ethymology of a word for instance).
This is possible throuh a dichotomous algorithm that is very fast, even with
64 000 lines per list ... unless I have to load repeatedly a subset of those
lines. I will first study better your ideas, and next I will see.
Bye.
My application is a dictionary, it's why I have so many lines. I need to be
able to browse through the listboxes of my application, so I'm not sure I can
load repeatedly a subset of records. Moreover, I have a lot of lists
containing diferent items (French word, Icelandic word, etymology, and so on,
and each of these lists is used in several parts of my application to help me
input data in textboxes (traduction or ethymology of a word for instance).
This is possible throuh a dichotomous algorithm that is very fast, even with
64 000 lines per list ... unless I have to load repeatedly a subset of those
lines. I will first study better your ideas, and next I will see.
Bye.