Apologies if this has been mentioned before, but haven't come across anything from my search...
I have a strange issue at the moment where when I debug and step through my code, as soon as the first declaration (DIM statement) is stepped over, the value is being set to something that doesn't exist! This is even before it has got to the code that sets the variable :-(
Now I can see when stepping through that it highlights the section afterwards, so it is almost like it is doing the next step when it carries out the initial declaration, which is fine, but it is setting the value to a value that is different to what my code says!
I have come to the conclusion that it is "holding" something in memory, as the value being set "used" to be the value before I changed it, so it isn't a completely random value...
I did find some reference to strange behaviours with this and it was acknowledged by MS as a bug which was addressed in Update 1, however I have installed that update and it is still the same.
If I run the executable, I can see that the correct values are reflected, so this does seem to be an issue when debugging.
Maybe I have some setting somewhere that "holds" on to values in memory??
Anyone else had this, and know what I need to do to fix?