hi all,
apparently, the exception is thrown when for example, i add a new row to the datatable then leave fields empty including columns which the AllowDBNull property set to False. i then try to add a new row or navigate to another row and that's when i get the error.
i've seen many forums giving work-around with this exception but i haven't any samples that really catches the exception.
the requirement is that
1. i need to some columns set AllowDBNull to False.
2. i need to prevent users from navigating away from a new record that has Not Nullable fields empty.
3. use bindingsource built-in events as much as possible.
can someone provide ways on how to go around this considering the requirements i have?
thanks.
apparently, the exception is thrown when for example, i add a new row to the datatable then leave fields empty including columns which the AllowDBNull property set to False. i then try to add a new row or navigate to another row and that's when i get the error.
i've seen many forums giving work-around with this exception but i haven't any samples that really catches the exception.
the requirement is that
1. i need to some columns set AllowDBNull to False.
2. i need to prevent users from navigating away from a new record that has Not Nullable fields empty.
3. use bindingsource built-in events as much as possible.
can someone provide ways on how to go around this considering the requirements i have?
thanks.