All:
For those of you who use the Macola ES Excel Add-In, you may have already discovered, or are just discovering, the effects of the recent critical update pushed April 10th by Microsoft.
Users will be getting a message: “Object library invalid or contains references to object definitions that could not be found”
According to the MS Knowledge Base, this is a known issue and the resolution is included in the KB article. After following the instructions on my computer (MacolaES 9.5.500, Excel 2010, Windows 7 x64) I am able to get Excel to work without the error message,the Excel reports integrated into the MacolaES package are working; however, I am not able to get the GL/Reports/Excel Add-In feature to work.
Since this is a fairly recent development I'm not finding much other info on this. I hope that this info saves someone else some time on their research, AND I sure hope that someone else that sees this can provide some additional insight in resolving the Add-In issue.
FYI,
Julie B.
(Not sure why this is doubling up .... sorry for the repetition)
For those of you who use the Macola ES Excel Add-In, you may have already discovered, or are just discovering, the effects of the recent critical update pushed April 10th by Microsoft.
Users will be getting a message: “Object library invalid or contains references to object definitions that could not be found”
According to the MS Knowledge Base, this is a known issue and the resolution is included in the KB article. After following the instructions on my computer (MacolaES 9.5.500, Excel 2010, Windows 7 x64) I am able to get Excel to work without the error message,the Excel reports integrated into the MacolaES package are working; however, I am not able to get the GL/Reports/Excel Add-In feature to work.
Since this is a fairly recent development I'm not finding much other info on this. I hope that this info saves someone else some time on their research, AND I sure hope that someone else that sees this can provide some additional insight in resolving the Add-In issue.
FYI,
Julie B.
(Not sure why this is doubling up .... sorry for the repetition)