Hello:
We have about 70+ forms and our testers keep making the same mistake -
they start typing into the controls before they create a new record.
We have been thinking about how to handle this situation. We thought
1) we would disable the controls until they added a new one or 2) we
would automatically create a new record when the BindingSource.Count
== 0.
We also have code that will automatically check that our users don't
move to the next record without first saving. Only one record is
displayed on the form at a time. If we add a new record when ther
BindingSource.Count == 0, the underlying DataTable will show an Added
row. So, when the user tries to move to the next record, they are
automatically prompted to save this added record. However, if they are
just navigating to a record, they don't intent to add a record every
time and are confused by the prompt to save. This is really annoying,
too.
So, that leaves us with the option of disabling controls until after a
a new record is created. However, this is a monumental task when you
have 70+ forms. And this isn't directly supported, so we would have to
write some code to do it.
We have also thought about not actually adding the row and leaving it
detached. But then we won't know when to actually add the row to the
underlying DataTable.
We are wondering how other groups handle this situation. Is it more
user friendly to disable the controls or automatically create a new
one? If it were truly up to me, I would redesign the forms to avoid
the issue altogether.
Thanks,
Travis
