Thanks, for the good stuff. I don' know much about VB, a UserForm may
be better for me. I've never really messed with UserForms. Right now if
I make a mistake filling in the information, I can't go back. It hasn't
been a big deal because there are only three input questions and the
form was made to access and complete quickly.
Like you said, a case may be best for me. There are eight different
possible states, ten possible products, and two options for the
replacement (obviously yes or no). Changing just one of the options
completely alters the output list. That results in alot of possible
lists being generated.
let me know what you guys think.
With 160 possible combinations, I suggest you stay away from trying to do it
all in one big logical structure -- it's just too hard to set up and
maintain that much detail.
If your lists are predefined for each possible combination, then some kind
of look-up might be better: populate a collection whose members are the
possible lists, and whose keys are constructed from the state, product, and
replacement values. Then you might have something along the lines of
pKey = cstr$(state) & cstr$(product) & IIF(Replacement, "Y", "N")
list = ListCollection(pKey)
If your lists are constructed on the fly, inferred from the various values
(eg, some elements are a function of the state, some of the product, etc)
then set up a function that returns the list given the state, product, and
replacement as arguments ---
Private Function GetList(State as string, Product as string, Replacement as
boolean) as array
....
end function
Called using
list = Getlist(state, product, replacement)
> Thanks, for the good stuff. I don' know much about VB, a UserForm may
> be better for me. I've never really messed with UserForms. Right now if
[quoted text clipped - 9 lines]
>
> let me know what you guys think.