>>>>
>>>>Right, but I have custom code in valid event of the grid, which I call from textboxes valid. Even with dodefault() in valid, I had refresh called.
>>>>
>>>>Do you think, it would be better to call custom grid method instead of Valid method? I think, I'll add a new method Validate to a grid, and make necessary changes...
>>>
>>>I don't know Nadya. All I know is valid usage is tricky and might catch you if you have say row level validation.
>>>Cetin
>>
>>I have table level buffering. I realized, that row level would not work, so I proposed some changes in our framework.
>
>Row-level buffering is near impossible to use correctly in grid because record become automatically updated as soon as grid is refreshed. Column.Refresh will cause auto-update too.
>
>As about Valid event of grid, it is fired when grid lose focus, as far as know, so probably it can cause no conflicts but just will be called twice - once from control (your manual call) and once from grid (automatic call as event). From the OOP point of view better make a custom method. Direct call of event (like button.Click) should be avoided with exception of special situations.

Hi Vlad,

I've realized all of this already (thanks to the recent threads) and just made necessary adjustments. Now I'm testing :)