Does this look properly normalized? Would it be impractical?

[BDibz]

Would this database design be properly normalized? I tried to separate things logically. My only concern is that on the input table - the table people will be using to update information about each Job Number during the morning meetings - they need to be able to see information from the Vista Table as well. Would it be possible to have a field tied to the related table without doing a subtable? For each job number in Input Table, I just want to display a field that shows the part number for that job in the same table. What would be a good way to do that?

Any other general suggestions?

[Minty]

Looks fine to me, I'm not sure I understand your concern over the Vista Table - you can pull information from that into a form / query to display when an appropriate comment is being made, in the format of a MainForm / Subform layout - where the main form would be the Vista table and the sub form the comments ?

[Micron]

I don't foresee any issues with the design either - save for bad naming. Special characters (save for the underscore) should be avoided.
See these or other pages that have naming information:

One source about how to name things - http://access.mvps.org/access/general/gen0012.htm
What not to use in names - http://allenbrowne.com/AppIssueBadWord.html
If you think you could benefit from other suggestions, I have links for understanding autonumbers, lookup fields and calculated table fields.