Sorry for the late reply.
We've been working on this issue, and haven't come to a conculsion yet. When I know the answer I will update this post also.
This was a downstream affect of the SQL collation used.
The stored procedure is getting updated to be collation agnostic in the next version of MVM. The *requirement* is to still use the standard US collation, but we're trying to move away from that thanks to all your input Ritch :-)