Hi again, after a few more community thread searches I think that the problem we have discussed within this thread is the same one as the one discussed here:
community.office365.com/.../75412.aspx
Also it seems like one of the latest office updates has caused the problem... Could you possibly produce a fix to this at MS, or how should we proceed?
