TesseractE
New Member
- Joined
- Nov 30, 2011
- Messages
- 38
Our IT group decided that it'd be fun to upgrade SOME of us to Office 2010 while leaving others on Office 2007.
Surprisingly, this is causing issues.
The big one is that we're using a shared file to record our daily work. It uses a few UDFs, and it seems that when the file is created in Excel 2010, opened and saved by a client using 2007, then opened again in 2010, it declines to activate the macros before giving up and giving an error because the macros aren't working.
Up until recently, the issue was minor, as it only affected a small handful of UDFs that could be easily refreshed by prompting a calculation after the sheet had been fully loaded. Recent necessary evils required more complication in the background formulas, and now this issue manifests itself with an 'Automation Error', rendering the sheet unusable to 2010 clients after it's been opened and saved by a 2007 client.
We're working on switching to an Access-based version of the same tool, but the certification for that is moving at the speed of bureaucracy, so we have to continue making do with Excel.
Are there any suggestions for how to handle this? So far, opening another file and activating macros on that file first seems to jump start the target file into action, but that's definitely not a permanent solution.
Surprisingly, this is causing issues.
The big one is that we're using a shared file to record our daily work. It uses a few UDFs, and it seems that when the file is created in Excel 2010, opened and saved by a client using 2007, then opened again in 2010, it declines to activate the macros before giving up and giving an error because the macros aren't working.
Up until recently, the issue was minor, as it only affected a small handful of UDFs that could be easily refreshed by prompting a calculation after the sheet had been fully loaded. Recent necessary evils required more complication in the background formulas, and now this issue manifests itself with an 'Automation Error', rendering the sheet unusable to 2010 clients after it's been opened and saved by a 2007 client.
We're working on switching to an Access-based version of the same tool, but the certification for that is moving at the speed of bureaucracy, so we have to continue making do with Excel.
Are there any suggestions for how to handle this? So far, opening another file and activating macros on that file first seems to jump start the target file into action, but that's definitely not a permanent solution.
