Class Definition Clashes
Using data-aware and non-data-aware versions of the same ActiveX control together in the same application presents a unique problem. The FlexCOM class generator will generate identical superclasses for respective data-aware and non-data-aware wrapper classes.
This problem is demonstrated in the COM sample application with data-aware and non-data-aware versions of the Calendar ActiveX control.
Solution
The solution is to edit one of the wrapper class packages and remove the class definitions of the wrapper's two superclasses (see COM Object Wrapper Classes). Since these superclasses are identical for both data-aware and non-data-aware wrapper classes, you can re-use the definitions for both wrappers. You will need to include a Use {package name} command to ensure that the superclass definitions are compiled into the class package where you deleted the identical copies.
One downside to this solution is that you will be modifying a package that was generated by the FlexCOM class generator. This is not as bad as it could be since you are quite unlikely to need to re-generate the modified package. It will be sufficient to only re-generate the unmodified package each time since all of the interface definitions are defined there and used by both wrapper classes.
Study the cComCalendar and cComDbCalendar class definitions in the COM sample application for more information.