We are on DLL version 2015.1.318.545. Is the bug fixed in this version?
One of our users (off-site) sent us an example of this bug from our production site just the other day. We have no way to reproduce as we don't have Excel 2007.
We are on DLL version 2015.1.318.545. Is the bug fixed in this version?
One of our users (off-site) sent us an example of this bug from our production site just the other day. We have no way to reproduce as we don't have Excel 2007.