So maybe something like:
---------------------------------------------------------------Sub Item_CustomPropertyChange(ByVal Name)
Select Case Name
Case "Division"
Call SetSubDivision
Case "SubDivision"
Call SetThirdBox
End Select
End Sub
___________
Sub SetSubDivision
Set objInsp = Item.GetInspector
Set objPage = objInsp.ModifiedFormPages("General")
Set SubDivision = objPage.Controls("cboSubDivision")
Select Case Item.UserProperties("Division")
Case "Ambulance"
SubDivision.List = Split("Air,NHS,Private,Vehicle Builder,Voluntary",",")
Case "Export"
SubDivision.List = Split("Distributor,End User,Ferno Group",",")
Case "Hospital"
SubDivision.List = Split("Distributor,MOD,NHS,Private",",")
Case "Industry"
SubDivision.List = Split("N/A",",")
Case "Mortuary"
SubDivision.List = Split("Distributor,Funeral Director",",")
End Select
End Sub
___________
Sub SetThirdBox
Set objInsp = Item.GetInspector
Set objPage = objInsp.ModifiedFormPages("General")
Set ThirdBox = objPage.Controls("cboThirdBox")
Select Case Item.UserProperties("SubDivision")
Case "NHS"
ThirdBox.List = Split("Option A, Option B",",")
Case "Private"
ThirdBox.List = Split("Option C, Option D",",")
(etc.....)
End Select
End Sub
---------------------------------------------------------------"Sue Mosher [MVP]" wrote:
> Yes, that's one of the characteristics of bound controls.
> The second Case block to handle a second property's value changes would go
> right after the first, as in the example at
> http://www.outlookcode.com/article.aspx?ID=38.
> > Sue Mosher
> > >
> "Amy Brooks" <AmyBrooks> wrote in message
> news:368AA6CF-2374-4D66-BBE8-622DAC1E50E4@microsoft.com...
> > Bound is when it saves the selections when closed?
> > If so, I think they are bound.
> > If they are, how would I go about adding another case block? There are
> > more
> > values now, is that still the way to go?
> > "Sue Mosher [MVP]" wrote:
> >
> >> Again, that's going to depend on whether the 2nd combo box is bound or
> >> not.
> >> If it is, you add another Case block to the CustomPropertyChange event
> >> handler to handle the change in that property. If not, you use the
> >> control's
> >> Click event. See the previously suggested article.
> >
> >> > >> Sue Mosher
> >> > >> > >> > >
> >
> >> "Amy Brooks" <AmyBrooks> wrote in message
> >> news:044BE2A3-61C3-47AA-A1C1-29B3BEB13388@microsoft.com...
> >> > Hi Sue,
> >> >> > Regarding the previous question, could I add more code to have a third
> >> > combo
> >> > box relate to the second?
> >> >> > Thanks,
> >> > Amy
> >
> >
> >>
>