Montly Production Shedule Report

[GolfingDuo]

I need to create a database and it has been a while since I have created a DB and I get some of this okay. It is so that I can create a schedule report. So far I think I need three tables. One is the machines. Two is the product schedule (how long it takes to produce X number of products). The last would be work orders. I think that pretty much covers the data.

I think most of the data can be maniputated by queries and that is even done on the report. The report as we all know is the reason for a database. If it was just about the data it would be simpler to do a spreadsheet. It could get fancy and make a pivot table. That output can be a calendar of sorts. What I would like to see is a weekly or montly report that have lines per machine with job orders lining up so that we can see any overlap or too long of a gap between workorders.

I am planning on having the database operator only need to punch in the workorder, number of items, and when the job is needed to be completed. In the output of the report I will have it do some math to determine how many days it will take to complete the workorder and enter that as a line in the calendar. With 33 machines this would probably be weekly since 33 lines in each day is quite large.

I am envisioning it as a single line beginning this day stretching to this day. It would be nice to color code it and print the workorder in the line. It would be a management tool for production managers to crack the whip.

Well anyway I have to go back to creating my tables and my desk. Thanks to anyone who might have an answer.

 

[Beetle]

Thanks to anyone who might have an answer.

An answer to what? You basically just gave us the entire scope of everything you want your database to do, but it's not clear if you even have a proper table structure yet. If you need help on table design, then let's stick to just that, but you need to give us a clearer picture of exactly what entities you're dealing with and how they relate to one another. Queries, forms and reports would not be relevant at this point.

 

[GolfingDuo]

It is very simple. Not a lot of meat and potatos in it. It won't need to.

Three tables.
table one - Machines one through thirty-three (no other data) no need for updates unless we add a machine to the total.

Table two - Tools/molds - all unique - data includes description, cycle time, how many items can be created in one 24 hour period. (the key data there is how many items in a 24 hour period). Only update is if we add another product to the manufacturing line (a new mold)

Table three - Work orders - Unique name, how many items and when does it need to be completed to include a fudge factor of in case or (oh sh*t)

Not a lot of structure there. I don't think that there needs to be. My report is what I am looking for. I know that Access can output to Outlook in some way. I have read it. I just haven't figured out how it does it. My purpose is to have a snap shot view of each machine (all at once) and the jobs they have pending. I want to make sure there is no overlap of jobs. If there is I can adjust the jobs around to accomplish the tasks. Some of the jobs will be just for inventory while others will be direct ship. This should include when the job will start to date it ends. That calculation will be done in the query. I currently can do it in Excel as a pivot table. Issue there is it is quite difficult to update and the current view don't show overlapping on the machine in a meaningful view.

Tables one an two get no changes to it. Table three is the only table that anyone inputs in. I know how to create forms and queries so really my only worry is how it prints out. I know that with as many machines that I have I would not be able to read a printed page of a calendar monthly picture or yearly one. Printouts will probably be for a week but that is not even the problem. As long as I can have an electronic picture of all the machines and workorders the operator/production manager can see what adjustments need to be made.

My vision of the output is a colored line that holds the workorder number/name that starts on the date it needs to begin and ends on the date it needs to end. For each machine would have its own unique line in the calendar the jobs scheduled for that machine would show up there. If I see overlapping then I need to adjust. Simple as that. It is a production manager's tool. Nothing more, nothing less. Maybe it should be just a form. If we try to print out a report that covers a full calendar month for 33 machines it would not be able to be read. I was thinking though if it were print preview we could zoom in and view it in pieces.