R
Ricky W. Hunt
VB.NET seems to be processing things in a different "order" than I'm used
to. For example, I had a problem (I don't have the exact code handy anymore
so it's just a "guess") where if I put the complete code in a single
subroutine it wouldn't work but if I put the part that wasn't working in a
subroutine, and called it after the first subroutine finished, would work
even though if you laid out the actual commands linearly ("in order") they
would be exactly the same. Does anyone know why this happens and what is it
"called"?
to. For example, I had a problem (I don't have the exact code handy anymore
so it's just a "guess") where if I put the complete code in a single
subroutine it wouldn't work but if I put the part that wasn't working in a
subroutine, and called it after the first subroutine finished, would work
even though if you laid out the actual commands linearly ("in order") they
would be exactly the same. Does anyone know why this happens and what is it
"called"?