G
Guest
Hi all,
Real issue for me here: I'd like to know where it would be best to put
validation and which are the events best suited to deal with such
record-related operations. There are many options, and I seem to be a bit
lost. Many people like the Partial Dataset class as opposed to putting
client-side/control-based validation, while others, its the opposite.
Do TableAdapters fit into the picture anywhere in terms of validation?
How about BindingSource? Should I use that to respond to "Adding New row",
"Deleting", "Modifying", etc... or should I use the DataNavigator? All this
is kind of confusing. Thus, the best place to put validation code and the
best place to capture record navigation (with the possibility to add some
logic). I'd like to use the ErrorProvider, etc...
What is the best practice/modern OOP way of doing things?
Regards,
Giovanni
Real issue for me here: I'd like to know where it would be best to put
validation and which are the events best suited to deal with such
record-related operations. There are many options, and I seem to be a bit
lost. Many people like the Partial Dataset class as opposed to putting
client-side/control-based validation, while others, its the opposite.
Do TableAdapters fit into the picture anywhere in terms of validation?
How about BindingSource? Should I use that to respond to "Adding New row",
"Deleting", "Modifying", etc... or should I use the DataNavigator? All this
is kind of confusing. Thus, the best place to put validation code and the
best place to capture record navigation (with the possibility to add some
logic). I'd like to use the ErrorProvider, etc...
What is the best practice/modern OOP way of doing things?
Regards,
Giovanni