I'll have to check out that book ;)
Anyway, if we go back to the root question of this topic (working with Oracle strings in VB), the answer really is that: Yes, this is the defined behaviour of Oracle, and you have to work with it at an application level by treating blank string as a special...