Link to home
Start Free TrialLog in
Avatar of bd9000
bd9000

asked on

Binding Navigator - how do you get Validate to fire when someone clicks the add button more than once?

I've been trying, once again, to do some of the simplest things with the BindingNavigator tied to a BindingSource and without generating errors.
One thing I can't seem to solve, it that if a user clicks the "Add" button on the BindingNavigator more than once, it attempts to save the previous record without firing the Validate event (and saves nulls even though they are trapped in the dataset partial class).
Clicking the Save icon, I can trap that click event and run a save routine and validation works just fine.
Since there seems to be no way to enforce validation rules (on the recordset) during this situation, I need to disable the add button after it is clicked once or somehow prevent the button from being active if the current record has not been saved or validated.
Code to follow - hopefully soon
ASKER CERTIFIED SOLUTION
Avatar of PlatoConsultant
PlatoConsultant
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of bd9000
bd9000

ASKER

I made the add button invisible as soon as it is clicked - I have some of my own logic now.  I guess I'm still surprised that the 3rd generation of bound controls is still unusable for real-world situations.  Unfortunately, I think there are too many people out there wasting inordinate amount of time finding all the work-arounds than just doing it the old-fashioned way (binding your own controls, write your own navigators). I would have had the project done weeks ago had I taken the old route. Geez!
Yaps Same with me i m using binding navigator but all the update and new record logic written by me.

actually it varies case to case,