Yes that is to be expected. This is an known issue with ActiveX controls and ProcessBook symbols.
This is documented under punchlist item PB1699 in our techsupport database.
Thanks...I kind of figured that was the case. If there was a way for me to group all these ActiveX controls into on "container" kind of variable that I could then act against in VBA, it would be cool....but I have not figured out how to do that, so for now I just set them one by one.