I have found the problem has nothing to do with Vista. The problem is in
Excel 2007. I have narrowed down the problem to an exact sequence and I have
issued a case with Microsoft and they have confirmed it to be a bug. I am
still waiting for the fix.

"Lambs" wrote:

Hi,

Please let me know if you managed to resolve this issue, as I think
something v. similar is happening on our system - but note we are not using
Vista, just XP.