VB 2010 Recompiling Corrupted Code

I've been getting wierd errors due to what appears to be compiler side errors, based on a corrupted compile that the compiler keeps using until i do something drastic like copy an entire module or function into noteback text editor, save my code, restart VB 2010, and paste it back in.[code]you may ask yourself, why do i even bother having the select case statement in the loop?c1 never gets high enough in the loop for your select case statement do anything (case: 99999, moreover u make c1 = itself, so there is no change in c1's value) The answer is that at one point i was making the select case statement do something, but when i tried to delete the entire select case statement, execution would simply fall through the loop.The for loop would only execute once.It would only do this with "optimizations enabled" outside of the debugger.Inside the debugger it worked fine, but every time outside of the debugger it would only execute once UNLESS i kept the meaningless select case statement in there.

Then, not wanting to see it there any more, i tried deleting the entire function (copying the text to notepad), recompiled (delete the calling line for the function), saved, exited, restarted systems (tried restarting system many times b4, but not b4 doing all this), opened VB, delete the select case statement out of notepad, copied the edited function from notepad to VB, recompiled and magically it finally worked.Understanding a little about optimization at machine lvl coding it appears the next c1 was optimized out by the compiler, instead using the end select statement to loop back to the top of the for loop.However, upon deleting the select case statement, it never reintroduced a loop back at the "next c1" statement, casuing execution to fall through.i've noticed this error occur about half dozen times (in other forms: by error i mean the comiler saving an optimization, but when the code that prompted the optimization is deleted, the compiler is not able to properly undo the optimization) while building my program, and my suggestion (rather than hunting down each of these errors), is to force the compiler to rethink the logic of of the program from scratch (which is what i thought it did already everytime i hit compile), but these experiments make me think its saving an error some where that only copying the function to note-pad and back again could make it purge.