Thank you, Pragati…
I’m not having any issues, as I was able to determine WHAT the C1CommandLink was doing, although I would appreciate a better understanding of this CommandLink process.
The reason is that I’m not comfortable with third-party controls making changes to my application without my knowledge and then not cleaning up behind itself (i.e. if you delete a C1Command out of the form’s C1CommandHolder object, it doesn’t removed the auto-created C1CommandLink and vice-versa, if you delete the C1CommandLink, it does nothing to the C1Command. Although, your application will throw compile errors if you’ve referenced these now deleted objects).
This seems to me to be an encapsulation violation of component building, meaning that if I only drop one (or create one through your designer interface) of your components on my Form, I expect that ALL interactions with it will be done only with the one I created and not through another control that was created silently.
Is there a ComponentOne video out there that can explain the C1CommandLink process?