I tried the example that you submitted in the other thread and failed to reproduce the behavior on a few different machines.
I have heard of this behavior before as you noticed in the other user's post, but we have come to a general concensus that the cause must be a combination of some of the following suspects in your current setup:
1) An underpowered machine (i.e. a pentium classic with 32MB of RAM running Windows 2000)
2) A graphics display problem
3) Too many other processes running at the same time as your Visual Basic application.
I know that these types of issues are often discouraging because of their random nature, but realistically they cannot be fixed by the developers if they are not reliably reproduceable so that the exact cause can be pinpointed.
This is why we are led to believe that it is some combination of system setup issues that is causing this.
If you are running a system that is "underpowered" for its current software setup, there really isn't much you can do except try to see if you can move to another, more powerful machine. As for the graphics subsystem you should always try to see if the latest driver for your video card resolves the problem. Regarding system performance as well, you should check to see if you have other unnecessary processes running that are inherently slowing down your system. Lastly, one thing you should also try is see if a somewhat similar system exhibits the same behavior so that you can use it as a test case to figure out what is causing the problem in your current system.
Jason F.
Applications Engineer
National Instruments
www.ni.com/ask
