OK thanks, it does seem to be the same problem that we fixed. Can you retest this problem when the next build is released?

regards John van Houten