Textbox.text, Input to Integer

[Keith]

I've been reading and looking on the internet - but I just can't fin
this. Perhaps I'm approaching this the wrong way - code-wise

I'm attempting to learn how "things" work in VBNET by creating
small app - 3 textbox objects. I want the user to input data int
textbox1 and textbox2 - and then click on a button - which will tak
the values to textbox1 and textbox2 and multiply them together. Th
result - displays in textbox 3

I think I'm running into problems where I'm attempting to convert th
textbox string (I guess it considers it a string by default) - int
an integer - so that I can take the 2 integers from textbox1 and
and multiply them together. Is the code below wrong? How do I ge
the data that the user inputs into the textbox - into a variable tha
is an integer

dim one as intege
one = val(textbox1.te xt

Does anyone see what I'm trying to do? Can someone show me a cod
sample of what needs to be done. I would think that this would no
be too difficult

[Russell Jones]

See Integer.Parse(s tring), or Double.Parse(st ring). All the numeric types
have a Parse method that parses a string and returns a number (if possible).

"Keith" <an*******@disc ussions.microso ft.com> wrote in message
news:7B******** *************** ***********@mic rosoft.com...

I've been reading and looking on the internet - but I just can't find
this. Perhaps I'm approaching this the wrong way - code-wise.

I'm attempting to learn how "things" work in VBNET by creating a
small app - 3 textbox objects. I want the user to input data into
textbox1 and textbox2 - and then click on a button - which will take
the values to textbox1 and textbox2 and multiply them together. The
result - displays in textbox 3.

I think I'm running into problems where I'm attempting to convert the
textbox string (I guess it considers it a string by default) - into
an integer - so that I can take the 2 integers from textbox1 and 2
and multiply them together. Is the code below wrong? How do I get
the data that the user inputs into the textbox - into a variable that
is an integer?

dim one as integer
one = val(textbox1.te xt)

Does anyone see what I'm trying to do? Can someone show me a code
sample of what needs to be done. I would think that this would not
be too difficult.

[Keith Wilson]

You could try

dim one as integer = 0
dim two as integer = 0
dim total as integer = 0
try
one = cint(textbox1.t ext)
two = cint(textbox1.t ext)
total = one * two
catch
'error doing calc or converting to int
end try

"Keith" <an*******@disc ussions.microso ft.com> wrote in message
news:7B******** *************** ***********@mic rosoft.com...

I've been reading and looking on the internet - but I just can't find
this. Perhaps I'm approaching this the wrong way - code-wise.

I'm attempting to learn how "things" work in VBNET by creating a
small app - 3 textbox objects. I want the user to input data into
textbox1 and textbox2 - and then click on a button - which will take
the values to textbox1 and textbox2 and multiply them together. The
result - displays in textbox 3.

I think I'm running into problems where I'm attempting to convert the
textbox string (I guess it considers it a string by default) - into
an integer - so that I can take the 2 integers from textbox1 and 2
and multiply them together. Is the code below wrong? How do I get
the data that the user inputs into the textbox - into a variable that
is an integer?

dim one as integer
one = val(textbox1.te xt)

Does anyone see what I'm trying to do? Can someone show me a code
sample of what needs to be done. I would think that this would not
be too difficult.

[Cor Ligthert]

Hi Keith,

I would do it something like this.
(I am an expert in making typos, so watch for that)

\\\
If IsNumeric(textb ox1.txt) andalso Isnumeric(textb ox2.txt) then
textbox3.txt = Cint(textbox1.t xt) * Cint(textbox2.t xt)
else
messagebox.show ("The values are not numeric")
end if
///

I hope this helps?
Cor

[Cor Ligthert]

Hi Keith,

Only to help, using a "try catch end try" for this kind of operatins is
not a good way to do.

The try .... cost a lot of time when there is an exception, while the only
error can be that the values are not numeric.

Use those exceptions catching for things you cannot see before (mostly
datahandling ).

Just an adittion, not ment as critique, so keep on helping.

Cor

[Chad Z. Hower aka Kudzu]

"Cor Ligthert" <no**********@p lanet.nl> wrote in news:OJzQULmPEH A.1392
@TK2MSFTNGP09.p hx.gbl:

The try .... cost a lot of time when there is an exception, while the only
error can be that the values are not numeric.

Unless you are in a loop the time overhead is insignificant. Getting results
from a user input and even triggering one catch is literally no overhead.

--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programmin g is an art form that fights back"

Get your ASP.NET in gear with IntraWeb!
http://www.atozed.com/IntraWeb/

[Cor Ligthert]

Hi Kudzu,

The try .... cost a lot of time when there is an exception, while the only error can be that the values are not numeric.
Unless you are in a loop the time overhead is insignificant. Getting

results from a user input and even triggering one catch is literally no overhead.

I do not agree, I said only use catch if there is no better alternative. And
mostly is it, when you make your programs well. Except if there is something
that you have no influence on.

In this sample by instance it will stop the program every time the user
enters an nonnumeric character, while there is a direct test for that.

Cor

[Chad Z. Hower aka Kudzu]

"Cor Ligthert" <no**********@p lanet.nl> wrote in
news:OP******** ******@TK2MSFTN GP09.phx.gbl:

> The try .... cost a lot of time when there is an exception, while the
> error can be that the values are not numeric.

Unless you are in a loop the time overhead is insignificant. Getting

results

from a user input and even triggering one catch is literally no
overhead.

I do not agree, I said only use catch if there is no better alternative.

No - you said "The try .... cost a lot of time when there is an exception"
which is the part I replied to.

If there is a non catch way to do it, of course us it. But the statement you
posted regarding performance is too general and there are a lot of learning
developers here. Thats why I clarified it.

I didnt say catch was a better choice in this situation.

--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programmin g is an art form that fights back"

Make your ASP.NET applications run faster
http://www.atozed.com/IntraWeb/

[Cor Ligthert]

Hi Kudzu,

Same idea and what is a lot of time, I see people here talking about things
which takes thousands of nanoseconds, and this can take parts of seconds
when it goes wrong, therefore.

However I am glad we agree.

Cor

[Chad Z. Hower aka Kudzu]

"Cor Ligthert" <no**********@p lanet.nl> wrote in news:#FEgoanPEH A.3708
@TK2MSFTNGP10.p hx.gbl:

Same idea and what is a lot of time, I see people here talking about things
which takes thousands of nanoseconds, and this can take parts of seconds
when it goes wrong, therefore.

It takes milliseconds at most. In a loop yes - but compared against the
drawing of the text in the text box and the user typing, we are talking ants
on the Titanic. ;)
--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programmin g is an art form that fights back"

Develop ASP.NET applications easier and in less time:
http://www.atozed.com/IntraWeb/