I don’t anticipate that it will ever deal with VBA compatibility. We’ve always had to do our own conditional compilation in code if that is an issue.
]]>When opening an Excel document using COM Automation which is supposed to supress all (ALL) screen I/O the Compatibility Checker is displayed in the background.
This causes automated processes to get “stuck” and there is no known way to fix this. It is extremely annoying to say the least. The implementation of this feature should adhere to all standards.
]]>Dave
]]>Your ADDIN works perfectly for me. It works for the new exported Excel files that I create everyday from our database.
Thank you!
]]>The thing is – how would you turn it off in that situation??
Need to glabally disable it when using some forms of automation….
]]>What I would prefer, actually, is an “Excel 2003 Color Scheme” so that I could use that by default. I happen to like those colors anyway. This would eliminate the error 99% of the time, leaving the 1% for when I actually do have a backwards-compatibility issue I should be concerned about.
Nevertheless, I wish I could tell Excel to ignore compatibility checking when it is a “minor formatting issue”
]]>