Hi Gene:

Those events do not occur after RowColChange because you can use RowColChange as a general validation event that works for existent objects and for dynamically added one.

Think of it as the KeyPress of the form, that prevail to the objects

El vie., 20 abr. 2018 4:40, Gene Wirchenko genew@telus.net escribió:

Hello:

  I now have the time to dig into grids again.  I hope this lasts

long enough for some real results. I took a look yesterday at "1001 Things ...", chapter 6 (Grids: The Misunderstood Controls). The number of gotchas is quite high.

  I find one particular thing especially weird.  Why, oh why,

does BeforeRowColChange fire before the active cell's Valid and LostFocus fire?

  To me, it seems obvious that the most likely reason why one

would deny a row-col change is because the active cell's validation failed. I will go further: why else would one deny a row-col change?

  My previous approach has gotten horribly baroque and still was

not enough.

  There are nasty things happening such as 1) the current

control's value not being assigned until after the BeforeRowColChange, 2) the validation using the previous value when I try to correct after some errors (but not always) but only for the first time, and it goes on.

  Correct one problem, and something else breaks.


  I am wondering if anyone would be willing to write a simple

example of a grid IN CODE to a spec I provide. This is the example that I am trying to implement. Maybe, I am overlooking something crucial. I sure have not seen any examples of grids other than trivial.

Sincerely,

Gene Wirchenko

[excessive quoting removed by server]