this a know bug in visual basic?

is there a work-around?