Sorry about the code macropod.

Thank you for taking the time to look at it and I will pass that on to the macro writers.

The macro is on a network share and is on many PC's so I don't believe it is a font problem, although it does reference this.
Since my last post I have done another thing, I downgraded a pc from Office 2010 to 2007, this user was getting the issue at least three times a day but since I have downgraded her she has not had it, not for four days now. Another user I have upgraded to Office 2013, this morning and she has not received the error as yet.

I am inclined to think that the error now relates to Office 2010 although I have not given enough time for the upgraded user to make a definite answer.

Are there any issue with office 2010 that you may know that might cause this?

Regards

Mark