In a VFP5 app, I have 3 MS ActiveX controls - TreeView, ImageList (from ComCtl32.ocx) and Calendar (from MSACal70.ocx) - if the client updates MS software (e.g., Office) and selects the option to install ActiveX controls, my app's ActiveX controls don't work.

The calendar comes up with everything black - was the 'default' of light gray - or with an error that Property VALUE is not found.
In the form which contains the Calendar, the OCX was actually changed!
Was supposed to bs MSACal70.ocx - changed to MSCal.ocx. It's the new version, but I don't want the new version, since I coded it to work with the old version.
The form which contains the TreeView and ImageList throws a Class Not Registered error for each control.

Should I just abandon use of MS ActiveX controls in my custom apps?
I can't recode and have each client reinstall everytime they install an MS update.

What is the way around this?