[JohnFogarty]

We've noticed the same thing in RobotC strangely enough while testing our elevator system.
I had to stop using certain methods I had constructed last season because of it.

also from what I'm understanding you are using a multi-case boolean switch?
and your button values change a pre-defined variable. allowing you to push 2 buttons to start the movement and push them again to stop it. If not.....then this may be a possible solution. I used muti-case boolean switches to allow multiple button press's to mean different things.

If this is a real problem... though I've only used LabVIEW on my FRC team.

There was a piece of code added to RobotC that allows the program to tell if the comm link is active. So I simply put all of my running code inside of a If statement which is running only when the comm is connected. otherwise it brings the robot to a halt. this really helps with the problems discovered last year with NXT brick lockups, from micro-electric power transfers.