Need a Preventative Maintenance (for machines) Access Db.

[Aurora]

I have created a Preventative Mtce Db for our factory machines, but I am
running into a problem. I have 3 db; (1) Basic Machine Infor; (2) Mtce
Operations (each machine may need different maintenance done on different
time schedules such as every 60 days, 90 days 6 months, or 1 year). These
two tables are linked by the Machine #. In the Operations db - each
operations is given a name which includes the machine # and a letter: Ex:
Machine 220, could have operations #220-A (for oil change due every 90 days);
220-B (for belt changes due every 120 days) and 220-C (for lubrication due
every 365 days) etc.

The 3rd db is a history of the mtce completed on each machine. This db
includes a work order #, date the pm was completed, & any comments made at
the time of the pm.

1. Emp runs a PM due report that tells him during a specified time frame
(01/01/07 - 01/30/07) that he enters, which pm's are due. Due dates are
based on the last PM completion date added to the frequency in which the
operation needs to be done.
2. When he decides which pm's he will do this week, through a form, he
enters the machine # and operation # and a Work Order (WO) # (automatically
assigned) comes up.
3. Using the WO #, he prints a work order that tells him the mach # and
which operation # needs to be done and any instructions that he made need.
4. Once the PM is completed, through a form and by the WO #, he enters the
date the PM was completed, his employee Id # and any comments he has
regarding the PM.
My problem comes with the fact that if you run the PM due report again using
the sames dates, the same list comes up - even though you have already
completed some or all of the PM's due. I do not know how to design this
program not to bring up the PM's that are completed.

Does anyone have any suggestions???? - Aurora

 

[aaron.kempf]

a) SQL Server has a built in 'Maintenance Plan Wizard'
b) Access Data Projects you don't need to 'compact and repair' the
backend
c) lose the training wheels; SQL Server is 1,000 times more robust
than Access MDB

 

[KARL DEWEY]

Due dates are based on the last PM completion date added to the frequency
in which the operation needs to be done.
Somehow the <<the date the PM was completed>> from the work order is not
updating the machine history.

 

[aaron.kempf]

if you used SQL Server then you could build a trigger so you could say
'no matter who changes this record; go and update this other record'

in Access; you just don't have that type of functionality