Can I use MS Works spreadsheet or other spreadsheet programs with BRC Addins?
For tools that are Excel addins, MS Excel is required.
MS Works is not Excel and does not support add-ins.
What versions of Excel are supported?
Many of our apps are Excel Add-ins that require Excel.
The apps are supported under various versions of Excel, from Excel 2000 – 2019 for Windows.
Each of the apps’ home pages indicates the supported versions of Excel in the Compatibility box.
After I install or manually load the Add-in, no menu or ribbon appears
Some relatively unusual settings can impact loading add-ins, as they disable the ability to run them. To check these settings, follow these steps:
Excel 2003: Choose Tools | Macro | Security | Trusted Publishers and then make sure the two available check-boxes are checked.
Excel 2007: To see this setting, go to Excel Options from the Office button in the upper-left corner of Excel, then Trust Center, Trust Center Settings, Add-ins, then make sure all three of the options there are unchecked. Pick both Com addins and Excel addins from the pick list at the bottom of the windows, and then make sure none are loaded Except BRC Addins. Then restart Excel.
Excel 2010 – 2016: Use steps similar to Excel 2007 to find the Trust Center Settings.
I get a message saying the addin is file losing it’s VB Project when I open Excel or load an Addin.
The message reads, “This workbook has lost its VBA project, ActiveX controls and any other programmability-related features.“
This happens when VBA for applications is not installed with Office. It is installed by default in most cases. To resolve the situation, reinstall Office or Excel and install the Visual Basic for Application components.
Why do I get a prompt for a password when closing Excel or taking some other action in Excel?
This is an Excel bug that happens to some Excel uses at different points. It is no longer very common and is generally caused by virus checker’s that try to decompile the addin. This triggers Excel to put up a password prompt. The fix is to teach your virus checker to stop checking Excel addins for viruses in this way or to get a different virus checker that behaves properly as it interacts with Excel.