Why can't you reference a column and row? Who knows... There are some things
you just have to accept, listboxes can only take arrays for multi-column
use, hence the suggestion of the list view. Besides it has a some great
features as you mentioned.
JD
Ben Rand wrote in message
news:DCD53163CD86CC0410263942DF20BE09@in.WebX.maYIadrTaRb...
Follow up on suggestions...
Frank and Jacob, I did go ahead with the ListView control which worked very
well (has a TON of great capabilities the VBA list box doesn't have) after I
stumbled around with it for a few hours trying to figure out how it worked.
I still don't understand why you can't just reference a particular
row,column in a regular list box and stick a value in there rather than
having to deal with an array. I'm trying to read delimited data out of a
.txt file which is then split up and put into columns in the list box. It
feels like I'm taking the long route by reading the info in, parsing it (to
split it into components), adding the parsed data into separate arrays, then
combining the arrays, THEN feeding it into the list box.
Joe and I exchanged an email or two behind everyone's back 🙂 but he did
reaffirm his statement about license to use that particular control in VBA.
Forgive me Joe, but I don't fully understand the implications--or how/if
that particular control would have to be licensed in order to be used. Maybe
others understand that better than I do, but I wouldn't mind more
explanation about this.
I do have a licensed VB Pro edition but usually develop my AutoCAD stuff in
VBA. Again, I don't really know if that's here or there.
Thanks for the input.
Ben Rand
"Ben Rand" wrote in message
news:6445AE43BE298E2C240D051D6E66E995@in.WebX.maYIadrTaRb...
> This should be really basic, but I want to populate a list box that has
two
> columns. I know you can feed an array into it using .List but I want/need
to
> feed the items into each column one at a time and .AddItem seems to give
me
> fits. Help?!
>
> Thanks,
>
> Ben Rand
>