null value in field on form

[laurat]

I am back with yet another question!!!

First, of all I will just say that an older db I am working on again (and the one I am referring to in this question) has a poor design. Most of that is due to specifications by the
higher ups here at work. There is a large table with a few forms based off of it. The first form is where users enter most of the info in a record. The next few forms are password restriced and accessed only by a few people to enter info into one or two fields of a record after a certain process is completed within the company. Finally here is the problem....some fields are required and the required property in the table is set to yes..... when a general user goes into the first form and enters the data and tries to exit, it brings up a message saying the record cannot be saved because a certain field is required and currently has a null value (these fields will be entered later on another)...this confuses me because the field the error message is referring to is not in the form or even on the query the form is based off of. I am not quite sure how to correct this problem and any thoughts would be appreciated. Thank you.

 

[Adrianna]

Okay....I think what you're saying is that you're getting an error message in a form which feeds back to a MAINtable which houses the fields from the user form and the restricted form.

Even thought the user form does not include the fields from the restricted form...once the user creates the new record...the field is automatically required...whether it is included on the form or not.

I would remove the required.yes from the field.

Or

BeforeUpdate on the form, assign the field a status:
Awating Imput, 0, Initialized....something like that.

 

[RV]

Or just set a default value for the table column....

RV