The biggest problem I see is that your company is wasting its IT budget on incompetence.
No. Worst case, you could corrupt the registry, messing up a user's SolidWorks settings, or delete/screw up a bunch of your company's SolidWorks files.
Other than that, there's nothing you could screw up with SolidWorks API that couldn't be equally as screwed up with VBScript and Windows API.
What can happen (which initially may be considered as the corruption of SolidWorks) is that your add-in throws some exception during the loading or during the execution which may cause SolidWorks application to crash. Usually the exceptions during the load are handled by SolidWorks and instead of crash it pops up the message that ‘Add-in cannot be loaded’ however sometime it may cause the SolidWorks to crash (for example missing Framework reference on the target machine). Anyways it is all not a corruption of the application. All you need is to disable the add-in and check – it won’t crash anymore.
Artem Taturevych, Application Engineer at Intercad (Australia)
translationXpert – add-in to translate SolidWorks models
myIntercad – an integrated tool for SolidWorks Professionals