Is there a reason this bug was terminated with no planned fix? We have replicated this problem on numerous code versions, not just the one specified in the bug.  Has anyone else encountered this and did you identify a resolution other than the workar...