Decimal Places FIGURED OUT

[twisted]

I have a Number UpDown box that everytime I type in..say 800 when I leave that box and click another it won't display 800.00

It just stays 800 even though I have decimal place properties set on 2.

I want users to type in 800 and when they hit on another box for it to display 800.00

I tried this but it didn't work:

Private Sub nudAmount_LostFocus()
nudAmount.Text = Format(nudAmount.Text, ".00")
End Sub

[Negative0]

Try this:

Private Sub NumericUpDown1_LostFocus(ByVal sender As Object, ByVal e As System.EventArgs) Handles NumericUpDown1.LostFocus
        NumericUpDown1.Text = Format(NumericUpDown1.Value, "#,###.##")
    End Sub

[Pirate]

What's the maximum value that can be set?
and it's wise to handle this validation rule in the validating event not the lost focus .

here's one way ,

Private Sub NumericUpDown1_Validating(ByVal sender As Object, ByVal e As System.ComponentModel.CancelEventArgs) Handles NumericUpDown1.Validating
        NumericUpDown1.Value = Decimal.Parse(Me.NumericUpDown1.Text, Globalization.NumberStyles.AllowThousands)
    End Sub

[twisted]

SEE HOW IT KICKS BACK TO THE DECIMAL PLACES WHEN THEY HIT CALCULATE
That is the only thing I can't figure out!

[Pirate]

Originally posted by twisted
SEE HOW IT KICKS BACK TO THE DECIMAL PLACES WHEN THEY HIT CALCULATE
That is the only thing I can't figure out!

Check if the event handler (nudAmount_LostFocus) is attched to nudAmount control ??

Second , did you try both ways above (they work fine for me) ??

[twisted]

Originally posted by Pirate
What's the maximum value that can be set?
and it's wise to handle this validation rule in the validating event not the lost focus .

here's one way ,

Private Sub NumericUpDown1_Validating(ByVal sender As Object, ByVal e As System.ComponentModel.CancelEventArgs) Handles NumericUpDown1.Validating
        NumericUpDown1.Value = Decimal.Parse(Me.NumericUpDown1.Text, Globalization.NumberStyles.AllowThousands)
    End Sub

It works for nudAmount, but not nudRate and nudYears. I get this error:
An unhandled exception of type 'System.FormatException' occurred in system.windows.forms.dll

Additional information: Input string was not in a correct format.

Option Strict On
Public Class frmFutureCalculator
    Inherits System.Windows.Forms.Form
    ' Assignment 2:     Gross Pay Calculator
    ' Programmer:       Brad von Oven
    ' Date:             June 11, 2004
    ' Purpose:          Create an application to calculate
    '                   the future value of an investment 
    '                   given the investment amount, interest rate, 
    '                   and number of years invested.  
    '                   Display future value in a read only text box.
    Dim IA, IR, YR, FVC As Double
 
    Private Sub cmdCalculate_Click(ByVal eventSender As System.Object, ByVal eventArgs As System.EventArgs) Handles cmdCalculate.Click
        IA = Val(nudAmount.Text)
        IR = Val(nudRate.Text)
        YR = Val(nudYears.Text)
        'Compute final value and put in text box
        FVC = IA * (1 + IR) ^ YR
        txtFuture.Text = Format(FVC, "$#####0.00")
 
 
    End Sub
 
    Private Sub cmdExit_Click(ByVal eventSender As System.Object, ByVal eventArgs As System.EventArgs) Handles cmdExit.Click
        End
    End Sub
 
    Private Sub cmdReset_Click(ByVal eventSender As System.Object, ByVal eventArgs As System.EventArgs) Handles cmdReset.Click
        nudAmount.Text = "100.00"
        nudRate.Text = "0.015"
        nudYears.Text = "0.5"
        txtFuture.Text = ""
        nudAmount.Focus()
 
    End Sub
 
    Private Sub nudAmount_Validating(ByVal sender As Object, ByVal e As System.ComponentModel.CancelEventArgs) Handles nudAmount.Validating
        nudAmount.Value = Decimal.Parse(Me.nudAmount.Text, Globalization.NumberStyles.AllowThousands)
    End Sub
 
    Private Sub nudRate_Validating(ByVal sender As Object, ByVal e As System.ComponentModel.CancelEventArgs) Handles nudRate.Validating
        nudRate.Value = Decimal.Parse(Me.nudRate.Text, Globalization.NumberStyles.AllowThousands)
    End Sub
 
    Private Sub nudYears_Validating(ByVal sender As Object, ByVal e As System.ComponentModel.CancelEventArgs) Handles nudYears.Validating
        nudYears.Value = Decimal.Parse(Me.nudYears.Text, Globalization.NumberStyles.AllowThousands)
    End Sub
End Class

[twisted]

This might help. Values are as follows:

nudAmount Max: 10000 Min: 100

nudRate Max: .25 Min: .015

nudYears Max: 15 Min: .5

I think it might have something to do with the last portion of the validating statement:

Me.nudRate.Text, Globalization.NumberStyles.AllowThousands

[taxes]

Hi,

In view of all the problems you are having with formatting numbers, I think you should concentrate on using the structure

(ss & st are declared as Double)

TextBox1.Text = FormatNumber(ss + st, 2) 'for numbers to 2 decimal places


and

TextBox1.Text = FormatCurrency(ss + st, 2) 'for currency signs.


When you have completed your project you can then investigate all the other ways you have been shown.
Remember KISS

[twisted]

Originally posted by Pirate
What's the maximum value that can be set?
and it's wise to handle this validation rule in the validating event not the lost focus .

here's one way ,

Private Sub NumericUpDown1_Validating(ByVal sender As Object, ByVal e As System.ComponentModel.CancelEventArgs) Handles NumericUpDown1.Validating
        NumericUpDown1.Value = Decimal.Parse(Me.NumericUpDown1.Text, Globalization.NumberStyles.AllowThousands)
    End Sub

I just had to change AllowThousands to AllowDecimalPoint

[taxes]

Hi,

Just a thought, If you are going to produce a programme to calculate future valuse of an invested amount, the quickest and shortest way is to use financial formula. You will find them on the net under "Annuity Formula".

There are formula for interest due monthly, quarterly or annually and in advance or in arrears.

[twisted]

I will do in future projects, but since this one is done it's staying just like this. Don't want to make my work any harder then I have to. I will use in the future though. Thanks it does look much easier.