<div>
that's a good point - nothing in the datasource then go out of the sub -but then that code would get launched for every cell that gets filled &quot;WHICH IS WHAT IS HAPPENING NOW&quot;- in the case of the .CELLVALUECHANGED event - when the FORM LOAD code is run - as is my limited understanding of VB.NET - well I can't over think this anymore - I like the REMOVEHANDLER and ADDHANDLER with the HANDLES clause removed - and will have to adjust future code as needed - thanx for the input!
</div>


<div>
Place a breakpoint in your event handler and check the call stack to see what causes the event to be raised.
</div>


<div>
I'm not going to call the event .cellvaluechanged at FORM LOAD at all - have DELETED - HANDLES clause! - but 1 more question and I promise I'm done with this issue -<br />
<br />
Where would you put the ADDHANDLER - once the FORM gets loaded<br />
My first choice will be at the very end of the FORM LOAD event!<br />
Is there a better way?
</div>


<div>
the end of Form_Load is usually the best place
</div>


<div>
Or it can be after you loaded the grid for the first time (if grid events)
</div>


<div>
ended up moving my code to the .mouseup event - and all works great!<br />
&nbsp;nice to know a little something about the events!
</div>


<div>
<div class="content wysiwyg-content">
My Project &quot;WHICH IS ALREADY A YEAR BEHIND SCHEDULE&quot; - mostly because of rewrites, mis-understandings, mis-interpretations, etc<br />
I am a little un-nerved about starting to REMOVE the HANDLES clause in some of my event procedures - although it fits the current purpose -<br />
<br />
&nbsp;wouldn't it also create code that should be auto-run and now it's not being run - because the HANDLES clause is no longer present?<br />
AND YOU WOULD HAVE NO WAY OF KNOWING THAT - OR IT WOULD BE DIFFICULT TO FIGURE OUT - MORE DEBUG NIGHTMARES<br />
<br />
which could cause say not properly formatted data in databases, etc - as an example with the .cellvaluechanged event?<br />
<br />
just trying to avoid more rework - because I'm quite a ways along with this FIRST vb.net project and time is running out!<br />
<br />
I guess what I'm trying to find out is - Is there a way to not touch the HANDLES clause and IN CODE tell the system not to run the said event!
</div>
</div>


My Project "WHICH IS ALREADY A YEAR BEHIND SCHEDULE" - mostly because of rewrites, mis-understandings, mis-interpretations, etc
I am a little un-nerved about starting to REMOVE the HANDLES clause in some of my event procedures - although it fits the current purpose -

 wouldn't it also create code that should be auto-run and now it's not being run - because the HANDLES clause is no longer present?
AND YOU WOULD HAVE NO WAY OF KNOWING THAT - OR IT WOULD BE DIFFICULT TO FIGURE OUT - MORE DEBUG NIGHTMARES

which could cause say not properly formatted data in databases, etc - as an example with the .cellvaluechanged event?

just trying to avoid more rework - because I'm quite a ways along with this FIRST vb.net project and time is running out!

I guess what I'm trying to find out is - Is there a way to not touch the HANDLES clause and IN CODE tell the system not to run the said event!

preceding with caution - with regards to REMOVEHANDLER and ADDHANDLER

Visual Basic .NET (VB.NET) is an object-oriented programming language implemented on the .NET framework, but also supported on other platforms such as Mono and Silverlight. Microsoft launched VB.NET as the successor to the Visual Basic language. Though it is similar in syntax to  Visual Basic pre-2002, it is not the same technology,