Please assist in setting up form properly

[Dave14867]

OK,

I have a database I am starting to create (Novice) and I want to do it right. It is for keeping track of labels inspected and the reject qty's. 1 table keeps track of the Information on a group of labels inspected then another is for the type of reject (Reject Codes) , and a third to keep track of the reject qtys.

I have a form set up with a subform and this seems to work, but honestly I don't like the appearance of the subform, they always look like they're unfinished if you know what I mean.

Can someone give suggestions on how to handle this if other than a subform. I thought about using text boxes but not sure how to handle that because there could be many different failures on any given lot of labels and I would have to create and display group of these text boxes for each failure code selected correct?

Also, let me know if the tables seem set up correctly for what I am attempting.

Database attached.

Thanks



Dave

Label Inspection.zip

[June7]

You could make the subform a Continuous View and rearrange the controls as you wish. Maybe the appearance will be more appealing.

Could have a textbox that displays the reject description. Expression in textbox ControlSource: =[Combo14].[Column](2)

Fix table relationships. Not using tblRejects. Why do you have a combobox with RowSource from tblLabelErrors?

[Dave14867]

June7,

tblrejects is a linking table to pass info between the 2 other tables, but I am retinking that now and have added 2 other tables, one for label size (at least 3 different sizes now) and the other for the printer used, of which there are currently 2, and will be more in the near future. After looking at it further tblRejects really isn't needed

Is the subform a good approach? I do like the way it automatically makes the connection correctly. I am not sure what you mean by make it a Continuous View

Thanks

Dave

[June7]

Yes, form/subform is appropriate.

Look at form DefaultView property. Experiment with the options.

[Dave14867]

June7,

I hadn't experimented with that control before, That could be very useful, if not in this form, possibly in the future.

Thank You very much for that suggestion.

Thanks

Dave

[Dave14867]

I have added some new tables and have run into some issues. If you look at Query1 you'll notice that "Description" is blank, I really don't want that field there because it already resides in the tblRejectCodes and I don't want to duplicate it. If I however put tblRejectCodes in the query, I get no results.

How do I get the "Description" from the tbleRejectCodes to properly appear in the results from the query and get the query to work when I put tblRejectCodes into the query?

Thanks
Dave

Label Inspection-expanded.zip

[June7]

tblRejectCodes should link to tblLabelErrors, not tblLabels. Link on RejectID fields because RejectID in tblRejectCodes is designated the PK. Need data in RejectID field in tblLabelErrors. Remove RejCode and Description from tblLabelErrors. Remove FailureID and RejectID from tblLabels.

Since you are not going to use tblRejects, might fix the table Relationships.

[Dave14867]

June7,

That seems to have done it. I had to redo the subform but it seems to work correctly now and the Query gives the expected/Desired results. I will start doing further testing on this tomorrow with some real data.

Many Thanks, you have been a great help.

Thanks Again

Dave