Re: restrict data entry until fields are complete

I agree with everyone here to some extent.
The problem lies in the fact that for the record to even be usable a
date and the type of service are required.

This is the filter on the forms, so if someone does not enter a date
or a type then the record is just a waste of space.

So either these fields are completed or the record should be deleted
they should not be allowed to enter anything until these are done.

At the same time if they move down to something they know and put it
in and then leave the record is tied to the person so even though its
incomplete they can do it later( like this ever happens )

I hate to say it but I agree with all of the arguements, again its
still the responsibility of the data entry person even though its not
their fault for receiving junk and then trying to force it in.





On Tue, 07 Apr 2009 20:43:30 GMT, "Tony Toews [MVP]"
<ttoews@xxxxxxxxxxxxxxx> wrote:

sparks <sparks@xxxxxxxxxxx> wrote:

I have a subform with 26 fields and it has 2 requirements.
Date and type

until these 2 values are entered I do not want them to enter any
partial records that will cause problems in the future.

What is the proper way to do this?

I disagree with your overall objective here. Stuff happens. It isn't always
possible to have all the data at the moment of entry. Or folks can be interrupted
for whatever reason, fire drill, coffee, lunch,etc.

Instead I'd suggest having another button opening a continuous form showing all these
data entry problems along with a command button on the continuous form opening the
data entry form.

I'd also run the same query that's behind the above continuous form as a count query
and display the number of invalid records on the main menu in a text box so folks
know there is a data entry problem that needs to be fixed.

Tony

.

Relevant Pages

  • Re: Aborting form entry
    ... Thank you for your suggestion but it appears not to work as required. ... I have a continuous form bound to a table. ... >> buffer table, using an append query, then binding the form to that buffer ... Aborting data entry is then easy. ...
    (microsoft.public.access.forms)
  • Re: Hiding bound controls
    ... Your questions should probably be in a separate table - one row per ... displayed for data entry in a continuous form. ... Duane Hookom has a good example of a survey/questionnaire database and the ...
    (microsoft.public.access.formscoding)
  • Re: more than 10000 rows in combobox
    ... Do you mean it is on a continuous form? ... with a textbox and modify the query that populates the table so that you ... Then, modify the form so that it does not allow additions, but has a "Add ... Record" button that takes you to a data entry form that allows you to use ...
    (microsoft.public.access.formscoding)
  • Re: restrict data entry until fields are complete
    ... You say "again its still the responsibility of the data entry person" ... button on the continuous form opening the data entry form. ... I'd also run the same query that's behind the above continuous ...
    (comp.databases.ms-access)
  • Re: continuous form and scrolling to view more columns
    ... The cursor just disappears out of view and reappears when it moves to the ... I have a subform that incorporates a continuous form. ... My users use the keyboard and not the mouse, to do data entry, make ...
    (microsoft.public.access.forms)