I think in the end it depends on what your validation needs are.
In my case, Cell Value Changed has done what I wanted/needed.
I used this event because I wanted to fire off a certain order of events, but only when the user changes the value of a cell.
This, therefore, undoes any action you perform in the handler.
Clear() End If End Sub Private Sub btn Save_Click(By Val sender As System.
Purchaseitems Dim i As Integer = 0 For Each row As Data Grid View Row In dgv Purchase Items.
EDIT The biggest thing about the Cell Validating event is that you can stop the user from leaving a cell, if the value entered does not pass your validation.
Public Class Purchases Implements IControl Event Public Purchase Order ID As Long = 0 Public dt As Data Table Public ds As New Data Set Private m View As Data View Dim _theme As Theme Event Changed() Private Entered By As Long Dim cmb Product Code As Combo Box Private p Code As String Public dv As Data Row View Public Product ID As Integer = 0 Public Product IDs As New List(Of Long) Dim combocolum As New Data Grid View Combo Box Column Dim namecombocolum As New Data Grid View Combo Box Column Dim Purchase Item ID As Integer = 0 Enum CBO_MODE NORMAL = 0 EDITABLE = 1 EDITABLE_WITH_NOTIFYCURRENTCELLDIRTY = 2 End Enum Const ALLOW_ADDS As Boolean = True Private MODE As CBO_MODE = CBO_MODE. Get Value(Purchase Order ID) If c Is Not Nothing Then dtp Purchase Date.
Click Try Dim check Purchase Order ID As Integer = 0 check Purchase Order ID = POSBLayer.