@deciptikon - quick follow-up question from a dinosaur. What is the difference between CDbl() and Convert.ToDouble(). Is the former being deprecated? Is there a reason why I should prefer one over the other?
What is the difference between CDbl() and Convert.ToDouble().
CDbl() is a little smarter by default in that it takes different numbering styles into consideration. You can get a similar effect with Double.Parse() and a formatter of NumberStyles.Any, with the understanding that the extra work has a runtime cost compared to Convert.ToDouble(), where the default behavior uses Double.Parse() with the less thorough NumberStyles.Float and NumberStyles.AllowThousands (if I recall correctly, of course. AllowThousands may not be default).
Ultimately it comes down to whether you want support for currency formatting, slightly more concise syntax, and don't mind depending on the Microsoft.VisualBasic assembly.
Implicit conversion are generally not a good idea. Even though Option Strict might be off it's generally a good idea to code like it is on, or to turn it on, and make all your conversion explicit(i.e. TextBox12.Text = agre3.ToString). It can save some confusion down the road.