Access - Required Fields Issue

[SantasLittleHelper]

I currently have 4 forms which different fields from the same table. These fields are 'required'.

When I go to save the form with the data inputted, it says I cant save it because there are some other required fields that are blank. - These fields are actually on a different form but are still for the same record in the table.

Is there a way to have the fields required only on certain forms?

 

[alansidman]

Why have multiple forms for the same record. This sounds contrary to acceptable RDBMS design. Usually, one form to a table. Look at this link for understanding good RDBMS design.

Fundamentals of Relational Database Design -- r937.com

 

[xenou]

Note that if the fields are marked required at the table level (in the table definition itself / table properties) then there is absolutely no way to save the record without all the required fields.

 

[HiTechCoach]

I currently have 4 forms which different fields from the same table. These fields are 'required'.


When I go to save the form with the data inputted, it says I cant save it because there are some other required fields that are blank. - These fields are actually on a different form but are still for the same record in the table.

Is there a way to have the fields required only on certain forms?

I agree with the others that you have a design issue.

Using multiple forms to manage the workflow is common. Setting fields to be required is good.

I believe the issue is with your table design not properly normalized

After 30+ years designing databases and creating accounting solutions, I have learned that your goal should be to only add records (transactions). Rarely modify existing records. That is what all this stuff in database normalization theory boils down to. This has been a "Best Practices" principle in Accounting for over 2000 years. I find it applies to all databases, not just accounting databases.

Based on what you have posted, I do believe that your table needs to be split up into a master table and at least one child/related table. Each form will manage a different record type. Note: A child table can hold multiple record types.

When the table is split up properly (normalized) then you should not have any issue the required fields.