Hello Philippe,
Thanks for your post, we appreciate the feedback! It appears that you are correct, in an older version of Vision, this was a problem. Since then the issue has been resolved, and the function should no longer display this behavior.
What version of Vision are you using? If you are using a current version, I would like to investigate this further. If it is an old version of Vision, you should be able to resolve the problem with the newer revision of the application.
Let me know if you need any other help!
Robert