Programatically fill a combobox

[Geir Baardsen]

Hi!

I have several textfiles on disk like:

Thing 1
Thing 2

etc...

On a form I have two combo-boxes. When user chooses from Combo1
(predefined items) I want the second combo-box to load the text files
according to which item user chooses in Combo1.

Is there anybody that know how I do this?

The reason why is because the textfiles contain so much text (and are
so many) I don't want to put it in the code like:

if Combo1.ListItem = 0 then

Me!Combo2.Items .Rowsource = "Thing 1;Thing 2; etc"
End if

The textfiles will also be altered from time to time, but will always
contain items belonging to Combo1.

Thanks!

Me.Name

[shumaker]

'Me!Combo2.Item s.Rowsource = "Thing 1;Thing 2; etc"'

How bout you read the items from the text file into an output string
stream(or just append to a regular string) using a loop that gets each
line into the string and appends a ';', then assign the string to
RowSource.

If I were you though, I would create a table and paste the items from
the text file into the table, then you can use an SQL query for your
row source:

SELECT MyListOfOptions FROM MyTable;

If you ever want to edit the options available, then it's as easy as
editing the table.

[Salad]

Geir Baardsen wrote:

Hi!

I have several textfiles on disk like:

Thing 1
Thing 2

etc...

On a form I have two combo-boxes. When user chooses from Combo1
(predefined items) I want the second combo-box to load the text files
according to which item user chooses in Combo1.

Is there anybody that know how I do this?

The reason why is because the textfiles contain so much text (and are
so many) I don't want to put it in the code like:

if Combo1.ListItem = 0 then

Me!Combo2.Items .Rowsource = "Thing 1;Thing 2; etc"
End if

The textfiles will also be altered from time to time, but will always
contain items belonging to Combo1.

Thanks!

Me.Name

You can string them together as mentioned in another post. A problem
may occur since the string that can be concatenated is limited. I'm not
sure...it may be 2048 characters.

Check out RowSourceType and then find the info for creating a
UserDefinedForm at. Then you can have large sets of data...but you
should be able to program.

[pietlinden]

Hey Steve Jorgensen or Lyle,
can you do this kind of thing in ADO? basically, read a delimited
textfile into a recordset-type thing (virtual table, essentially) and
then assign the result as the rowsource for the combobox? I would
think that you could call it by doing something like

Function CreateList(byva l strFileName as string) As ADODB.Recordset
.... or some such thing.

[Lyle Fairfield]

pi********@hotm ail.com wrote:

Hey Steve Jorgensen or Lyle,
can you do this kind of thing in ADO? basically, read a delimited
textfile into a recordset-type thing (virtual table, essentially) and
then assign the result as the rowsource for the combobox? I would
think that you could call it by doing something like

Function CreateList(byva l strFileName as string) As ADODB.Recordset
... or some such thing.

Surely the listbox simply translates the "recordset-type thing" to a
string anyway, so why would one translate the string to a recordset first?

Assuming you can read the textfile just set the row source type to
valuelist, and the rowsource to the string. I often do my list and combo
boxes this way even when they are based on a query.
--
--
Lyle

"The aim of those who try to control thought is always the same. They
find one single explanation of the world, one system of thought and
action that will (they believe) cover everything; and then they try to
impose that on all thinking people."
- Gilbert Highet

[Br]

In news:Eh******** *************@r ead2.cgocable.n et,
Lyle Fairfield <ly******@yahoo .ca> said:

pi********@hotm ail.com wrote:

Hey Steve Jorgensen or Lyle,
can you do this kind of thing in ADO? basically, read a delimited
textfile into a recordset-type thing (virtual table, essentially) and
then assign the result as the rowsource for the combobox? I would
think that you could call it by doing something like

Function CreateList(byva l strFileName as string) As ADODB.Recordset
... or some such thing.

Surely the listbox simply translates the "recordset-type thing" to a
string anyway, so why would one translate the string to a recordset
first?
Assuming you can read the textfile just set the row source type to
valuelist, and the rowsource to the string. I often do my list and
combo boxes this way even when they are based on a query.

Isn't there a limit on the length that string can be?
--
regards,

Bradley

A Christian Response
www.pastornet.net.au/response

[Lyle Fairfield]

Br@dley wrote:

In news:Eh******** *************@r ead2.cgocable.n et,
Lyle Fairfield <ly******@yahoo .ca> said:

Assuming you can read the textfile just set the row source type to
valuelist, and the rowsource to the string. I often do my list and
combo boxes this way even when they are based on a query.

Isn't there a limit on the length that string can be?

I can't comprehend a list box with so many choices that it approaches
any limit whatever, After 20 or so choices I find a different way. A
list box of a few thousand items is, IMO, quite ludicrous. SO my answer
is, "Dunno, Don't Care!".

There is a limit to the size of any list. Of course that's not including
the list of Texas executions which is infinite, but these are Divine
works of Men of God!

--
--
Lyle

"The aim of those who try to control thought is always the same. They
find one single explanation of the world, one system of thought and
action that will (they believe) cover everything; and then they try to
impose that on all thinking people."
- Gilbert Highet

[Salad]

Lyle Fairfield wrote:

Br@dley wrote:

In news:Eh******** *************@r ead2.cgocable.n et,
Lyle Fairfield <ly******@yahoo .ca> said:

Assuming you can read the textfile just set the row source type to
valuelist, and the rowsource to the string. I often do my list and
combo boxes this way even when they are based on a query.

Isn't there a limit on the length that string can be?

I can't comprehend a list box with so many choices that it approaches
any limit whatever, After 20 or so choices I find a different way. A
list box of a few thousand items is, IMO, quite ludicrous. SO my answer
is, "Dunno, Don't Care!".

I agree a few 1000 items is overkill. 20 choices? What happens if you
have 21 items? A list/combobox can handle more easily enough.

If you have a few rows but lots of columns you run out of string space.
The best way to do it is to create a user defined function. Using a
string is useful for small numbers of rows/cols.

There is a limit to the size of any list. Of course that's not including
the list of Texas executions which is infinite, but these are Divine
works of Men of God!

[Alan Webb]

Guys,
Whatever happened to callback functions. These were all the rage with
Access 97. If they are still supported then you can supply the data to your
function any which way. The mvp site should have samples of these.
--
Alan Webb
kn*******@SPAMh otmail.com
"It's not IT, it's IS"

"Geir Baardsen" <ge***********@ hotmail.com> wrote in message
news:35******** *************** ***@posting.goo gle.com...

Hi!

I have several textfiles on disk like:

Thing 1
Thing 2

etc...

On a form I have two combo-boxes. When user chooses from Combo1
(predefined items) I want the second combo-box to load the text files
according to which item user chooses in Combo1.

Is there anybody that know how I do this?

The reason why is because the textfiles contain so much text (and are
so many) I don't want to put it in the code like:

if Combo1.ListItem = 0 then

Me!Combo2.Items .Rowsource = "Thing 1;Thing 2; etc"
End if

The textfiles will also be altered from time to time, but will always
contain items belonging to Combo1.

Thanks!

Me.Name