from my TAM: I received from our View SME is that this is a known bug that was fixed in version 5 of View.
