I would say storing it in a table would be better. Create a table to store the maintenance records and then upon opening the file you could make a script to check maintenance and alert you if it is due.
thanks for your response!
actually, that's how i have it set up for maintenance as it comes up. once the due date alert is flagged, it prompts our coordinator to generate a work ticket. once that ticket is generated, it closes the maintenance, reseting the future date, and logs the work in a separate table.
what i'm hoping to achieve is getting a projected maintenance report for our team. to say, for fiscal year 2011, it will show the maintenance that it will expect us to do, month by month. the best outcome i can think of is something like google calendar, if you set up a weekly meeting, you can go months into the future and the meeting will still be there.
again, thanks with any help.
In that case, store a number in a field.
Say field called "maintenanceDays" = 30
Then, another field called LastMaintenance.
Then, build a report with a table where you can load the last maintenances from your history table, PLUS another 12 cycles for instance with a loop,
set variable $counter ; 1
Set dateField ; LastmaintenanceDate + maintenanceDays
Exit Loop if $counter > 12 (or get the number of remaining months, however you want to do it)
Or get t