Form design advice

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I currently have a form with many, many text boxes and drop down boxes. As it
stands all the fields are bound to one of my tables. At the top of the form I
have a lookup box with an account code in it (this field is required).

On the form load I have it go to a new record. The purpose is so that the
user can either input a new record immediately or click the drop down box to
select an existing record.

This is the problem that I am having:
My users are starting up the app, and then clicking on one of the many drop
down boxes or check boxes. Then when they go to select the company code at
the top it gives them an error message that states the company code can not
be null.

Access thinks they are inputting a new record even though they aren't. When
they click the drop down box to select a real record it causes the problem.

Any ideas how to fix this?
 
James said:
I currently have a form with many, many text boxes and drop down
boxes. As it stands all the fields are bound to one of my tables. At
the top of the form I have a lookup box with an account code in it
(this field is required).

On the form load I have it go to a new record. The purpose is so that
the user can either input a new record immediately or click the drop
down box to select an existing record.

This is the problem that I am having:
My users are starting up the app, and then clicking on one of the
many drop down boxes or check boxes. Then when they go to select the
company code at the top it gives them an error message that states
the company code can not be null.

Access thinks they are inputting a new record even though they
aren't. When they click the drop down box to select a real record it
causes the problem.

Any ideas how to fix this?
Click to expand...

Why would you think that entering data in a bound control on a bound form is
not "inputting data"?

If you have the form opening to the new record position and they start
messing with the ComboBoxes on the form they they ARE inputting a new
record. The form will attempt to save that record when they try to go to a
different record or close the form and if they didn't enter enough data to
constitute a legal record then they will get an error.

Inform your users that if they have no intention of creating a new record to
STOP messing with the controls. If they do anyway and get that message show
them how to cancel the record by pressing <Escape> a couple times.
 
Back
Top