required value

  • Thread starter Thread starter mark R.
  • Start date Start date
M

mark R.

What alternative ways are there to handle "required value"
(for fileds that are not primary keys, of course)
other than setting the property to "yes"?

ONE IDEA I HAVE:

I have certain fields that must have a required value such
as date-of-birth. But if the user starts a record and
inputs a dozen fields, but just can't put in the date-of-
birth until tomorrow, it will frustrate the user to lose
all that data that was available. If I could set a dummy
flag field to "ON", signifying that a "pseudo-required"
field is cuurently empty, I could query the table and keep
an ongoing list of records that are "incomplete" and
display them in a subform for the user to be reminded that
they have to go in and supply that date-of-birth.

PseudoCode:

If required value property is set to yes and user saves
record anyway, then RUN:

or maybe

Upon save_RECORD
RUN:

If any of the following fields (date-of-birth, address,
telephone munber) are empty;
Then set dummy_flag_field_ to "YES"

Query table for all dummy_flag_field = "YES"
display in subform
 
Nice concept Mark.


mark R. said:
What alternative ways are there to handle "required value"
(for fileds that are not primary keys, of course)
other than setting the property to "yes"?

ONE IDEA I HAVE:

I have certain fields that must have a required value such
as date-of-birth. But if the user starts a record and
inputs a dozen fields, but just can't put in the date-of-
birth until tomorrow, it will frustrate the user to lose
all that data that was available. If I could set a dummy
flag field to "ON", signifying that a "pseudo-required"
field is cuurently empty, I could query the table and keep
an ongoing list of records that are "incomplete" and
display them in a subform for the user to be reminded that
they have to go in and supply that date-of-birth.

PseudoCode:

If required value property is set to yes and user saves
record anyway, then RUN:

or maybe

Upon save_RECORD
RUN:

If any of the following fields (date-of-birth, address,
telephone munber) are empty;
Then set dummy_flag_field_ to "YES"

Query table for all dummy_flag_field = "YES"
display in subform
Click to expand...
 
Thanks, help me nail down the pseduo code part:

Will it work that way? I mean, if the user does not fill
in date-of-birth, will ACCESS handle all the error
messaging and I have no code to write, telling the user it
is a required field and let the user close the form or
move to the next new record?

I am thinking I want to direct the error handling process
so before hte user moves on to the next new record or
closes the form, I will RUN:

PSEUDO CODE:
ERROR_HANDLING:
Field required.............do you want to save the
records anyway?
Can you envision the code I have to write?
 
Back
Top