This is probably related to something that seems to get reported every couple of months: Visual Basic apparently can't cope with a secondary monitor that is positioned left of or below the main monitor (such that it uses negative coordinates). Nor can it handle touchscreens, gamepads, etc. These problems mostly seem associated with TreeView Controls (or whatever they're called), thus the economics window freaking out.
(Was it really essential to drop a thread like this in Mechanics rather than somewhere more appropriate?)