This issue must have been resolved in one of the latest software updates. I haven't been able to reproduce this error anymore.
Thanks,
Bill
