Hi Andreas,

This is a known issue in OrderEntry 8.0A (050530). A hotfix for this problem is being sent out to anyone who has reported this problem.