Making a form more user-friendly. Managing multiple subforms.

[TrainingExcellence]

I have a database that tracks lockout/tagout information for machines at the manufacturing facility where I work. I have created the form pictured below for inputting the data. The problem is the form is not very user-friendly, but I don't know how to make it better without compromising its functionality. Any design tips?

[mike60smart]

Hi

Can you upload a zipped copy of the Database?

[TrainingExcellence]

I have tried repeatedly to upload the file to the File Upload Manager, but it is not showing up. So I shall have to share the folder via OneDrive: https://campbellsoup-my.sharepoint.c...JjORw?e=eW7z4P

Thanks!

[ssanfu]

Tried to download the dB from OneDrive 4 times and each time got an error - "Not a valid Archive". Care ti re-upload the Archive?
Create the zip, then, on your computer, try to extract it.

Did you do a "Compact & Repair" before compressing the dB?

[June7]

I get 'invalid file' error when I try to open the zip. And when I try Extract it tells me zip is empty. If this file really is 51mb then certainly can't upload to forum.

[TrainingExcellence]

My apologies! Try this: https://campbellsoup-my.sharepoint.c...Ne3fA?e=K22V5B

[June7]

That worked.

Why do you say this is not user friendly? What would you like to see different?

[accesstos]

Have you ever think a step-by-step wizard?

[TrainingExcellence]

That worked.

Why do you say this is not user friendly? What would you like to see different?

My primary concern is the ease with which one can make a data entry error. If I want to add a hazardous energy or lockout point to Procedure B, for example, I have to be sure to select Procedure B before entering data into the other subforms. But it isn't obvious which procedure has been selected. I, as the database designer, can manage without problem, but I want to make this is simple enough that it someone with very low computer skills could use it.

[TrainingExcellence]

Have you ever think a step-by-step wizard?

How difficult would it be to create a wizard? Is there a tutorial or other resource you recommend?

[June7]

If you have relationships established and enforce referential integrity, Access can nag users when they try to enter a child record without first having parent record. They'll eventually learn how to avoid those annoying popups.

Otherwise, the more 'user-friendly' the more code. Can manage availablility of subforms based on value of field in parent form. For instance, if Procedure Is Null, disable the related subform, etc.

[accesstos]

How difficult would it be to create a wizard? Is there a tutorial or other resource you recommend?

I think it's easier than you expecting.
Take a look in attachment a sample with a tab control, setting it's Style to None.

Cheers,
John

[ssanfu]

I was going to suggest disabling sub forms, but June7 already suggested that.

My idea:
In your first post you divided the form into 6 steps.
I would have all sub forms and the save button disabled and locked until the 4 controls in step 1 are filled in, then unlock and enable the procedure sub form. After a procedure is selected (step 2), enable and unlock other sub forms. Continue enabling and unlocking sub forms as entries are made.

[TrainingExcellence]

I think it's easier than you expecting.
Take a look in attachment a sample with a tab control, setting it's Style to None.

Cheers,
John

Thanks @accesstos! I like it a lot. Here is where I'm at with the form. There is more to do, but it definitely looks better.


I like your suggestion, @ssanfu, because as is someone could inadvertently add lockout information for a machine without first entering the machine. Unfortunately though, I don't know Access VBA well enough to disable/enable command buttons by criteria.

Here is the link to the latest database: https://campbellsoup-my.sharepoint.c...sG1gQ?e=9mlZk5

[June7]

Code to disable objects is simple. The real trick is figuring out what event(s) to put code into.

I give subform containers names like ctrProcedure, ctrEnergy and comboboxes like cbxModel.

So, for instance, main form Current event could have:

Me.ctrProcedures.Enabled = Not Me.NewRecord
Me.ctrEnergy.Enabled = Not Me.NewRecord

Then code in cbxModel AfterUpdate event:

Me.ctrProcedures.Enabled = Not IsNull(Me.cbxModel)
Me.ctrEnergy.Enabled = Not IsNull(Me.cbxModel)