Re: Coding logic
- From: KARL DEWEY <KARLDEWEY@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 24 Apr 2007 14:50:02 -0700
In your ServiceReq table have a field that defines the schedule type ---
1 - Floating - Based on last completion
2 - Fixed - Based on last schedule
3 - Duplicate - Similar to fixed but generates a new task (work order) even
if old one is not completed.
Use criteria in append or update (for those that are flagged to do again)
which date is used in calculation for the next due date.
--
KARL DEWEY
Build a little - Test a little
"MikeJ" wrote:
In most cases, such as checking building temperatures, the task will simply.
be marked as done, and a new due date generated. In a few cases, there will
be a value to be stored. If a task is not marked as done, it should stay in
the report, perhaps marked as "overdue" until it is completed. I want the
next due based on the previous due date, rather than having the task just
keep getting moved out further.
"KARL DEWEY" wrote:
Are you planning on just updating a single record for each item or creating
new records for each item as each PM comes due?
If creating new records each time for the PM then are you creating the new
record without regard as to whether the last PM was accomplished? Or
scheduling from last scheduled date or last accomplishment?
If creating new records then use an append query and caluclating next due
from either completed or old scheduled date.
--
KARL DEWEY
Build a little - Test a little
"MikeJ" wrote:
Sorry if my post was a bit vague.
I am using forms for users to populate the tables.
I need to generate a daily pm *** (report) with the daily tasks, plus
whatever weekly, monthly, etc. tasks happen to be due for a given date. My pm
tasks table has a "last date done" field, and a "next date due" field. The
last date done field needs to update as task(s) are marked as done, and
generate a new next due date.
Only tasks that are due should show up on the report.
Thank you
"Jeff Boyce" wrote:
Mike
"Coding" implies that you expect to write code. Why? What is it that you
want to do that an Access form doesn't let you do?
Regards
Jeff Boyce
Microsoft Office/Access MVP
"MikeJ" <MikeJ@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:058EC3B8-A581-46A3-B2F9-5ECB2497AF0D@xxxxxxxxxxxxxxxx
I am trying to put together an application to track preventive maintenance.
The basic tables are: Location, Equipment, and Task; these are then
brought
together as a specific pm task, such as: change oil in generator, etc.
The various tasks are assigned a frequency such as: daily, monthly,
yearly,
etc. or can be assigned by miles or hours of run time.
I am looking for suggestions on the best way to code this. My experience
in
coding is minimal, and the best I have been able to come up with seems
very
cumbersome.
Any help would be greatly appreciated.
Thank you.
- References:
- Re: Coding logic
- From: Jeff Boyce
- Re: Coding logic
- From: MikeJ
- Re: Coding logic
- Prev by Date: Re: Invalid Outside Procedure Error Message ***HELP ;)
- Next by Date: Re: Keeping Tracking of who's adding new data..
- Previous by thread: Re: Coding logic
- Next by thread: Validation and subforms
- Index(es):