I'm sorry for the awfully slow response to this thread.
Obviously, some time has passed since you posted this issue, and the 1.0.2 patch has since been released as well. I'm not sure if this has been resolved, but I logged it as TT # 2302.
Thanks,
Steve