hi Greg

You are on the right track. Here is some advice that will come in handy as you progress with this database:
1) Shorten the table names. Remove all words that are assumed. I would name your three tables as follows:
    ShiftT, StageT And LogT.
2) Have Lookup tables for fields that the user selects from: shift, technician, am/pm etc.
3) start building your forms from the bottom up. Build the logF first. Then the StageF finaly the ShiftF

Also, use reasonably short field names and make sure to avoid any reserved words. Check this.

Greg

Good suggestions from Sami!

I would add the following suggestions:

- Don't let your design decisions be dictated by past design decisions.  (ie. the attached image looks like an Excel spreadsheet created by someone from the past.  Does it have to look like this?  Create your forms and reports to meet the specific needs of the workers.  You can create as many forms or reports as needed for different users)

- There are many ways to put together "your lego's".  Talk to your team members, find out what exactly they need, what would help them, etc.  This includes your supervisors and managers.  Rick has a beginner video starting a database where he talks about get all the forms and information currently being used.  Find out what people actually need what information from each part.  For example, do workers in Stage 3 need to to see field values from Stage 1?  I don't know that answer, maybe they do, but the point is to really flush it out to build forms and reports that meet the user needs.

- This is Access... you can build as many forms and reports as needed for various personnel.  Don't feel locked into 1 way of setting this up.  Give the technicians what they need, give the supervisors what they need, etc.  That's the great thing about a database, you're not locked into how the information is entered or presented.

-Raymond

Greg

Some more thoughts to help sell this to your team:

- I'm assuming there are specs associated with these fields, you can add conditional formatting to help clue your techs in on parameters that out of spec.

- I would add fields to the Table to capture the time and technician who inputs the data.

- Do you need to trends?  After a set of fields are recorded, you can have a form with a graph come up showing the trend.

- Does a supervisor need to review any of this data?  You can have a form showing unreviewed or UNSAT data with a field for follow up actions taken.

- For manual additional, you can link your database with your site's Safety Data Sheets for quick reference by the technicians.

- Be careful with generic information in your database.  ie. "Cone pump must be checked for proper operation..." this might be good enough depending on training.  What might work better is defined descriptions of what "proper operation" is.  ie. no abnormal noises, vibrations, not hot to touch, good suction/discharge pressures or flows, etc.  This might help over time trend how long before certain observations are made before maintenance needs to be performed.

Hope some of this is helpful.

-Raymond

I agree with Sami about keeping the names shorter. Good call from Raymond too on not forcing the form layout to match the old paper version. You don't know how many times I worked with companies that insisted that the database looks like their old system or even their old paper forms, which were horribly inadequate or inefficient. The best thing about building a new database is that you can make it work and flow like you want it to.

I'd also toss in lookup tables for any fixed lists (like shifts or AM/PM) and timestamp/tech fields for tracking entries. Those little touches make life a lot easier when you get to reporting and maintenance.

Thanks for all the great advice! I’ll be shortening my table/field names, adding lookup tables, and building forms from the bottom up as Sami suggested. Raymond, your ideas on breaking free from the paper form layout, adding conditional formatting, timestamps, and trends are really helpful. Richard, I appreciate the reminder to design for efficiency and make reporting easier. This feedback gives me a clear direction — thanks again!