Keith Clark wrote:
Hey Drew,
Well, I've told my user the pattern in which they should enter data and
all seems well now. Not sure how they were going wrong though. I've
made sure that the tab order also goes in the correct order.
I'll have to wait to see if their are more problems.
Thanks for the feedback. I was pretty sure I had it right!
Great - I recalled something after I posted the earlier email. A blunder
I managed to make a while back:
A data input form with Master / Sub forms connected to 2 tables that
formed a One to Many relationship. It displayed only data from a single
record at a time. (the master and sub form where both detail forms in
other words)
I managed to setup the form in such a way that when in the sub_form
controls entering data in the last control of the sub_form cycled back
to the first control in the sub_form. (Of course sometimes that is
exactly what you want to happen)
Further (and here is the contributing factor to the problem) there was
no data navigator attached to the sub_form.
SO - what would happen is that the user could actually enter a second
record in the many table - without realizing it. Remember what I said
about the auto_commit - well it works for a single form also, so when
that wrap around happened on the sub_form data for the first (current)
record was written and a input for a new record started.
Later if the form was opened it displayed the first record again - it
looked as if the data entry from the previous session was lost - it
wasn't - the form was simply not displaying it - no data navigator, so
nothing to tell the user there was multiple records in this table
related to the master form's record.
Just passing it along as a FYI.
Best wishes,
Drew
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
