Cool. Thanks for your help!
David E Jones wrote:
On Jun 4, 2008, at 12:47 PM, Adrian Crum wrote:
One thing to keep in mind: the way WorkEfforts are designed a single
WorkEffort as a task or whatever can have various sub-WorkEfforts
associated with it.
Then there would have to be code to cr
On Jun 4, 2008, at 12:47 PM, Adrian Crum wrote:
One thing to keep in mind: the way WorkEfforts are designed a
single WorkEffort as a task or whatever can have various sub-
WorkEfforts associated with it.
Then there would have to be code to create sub tasks when intervals
are passed. That
David E Jones wrote:
On Jun 4, 2008, at 11:51 AM, Adrian Crum wrote:
It appears to me that there is a one-to-one relationship between a
fixed asset maintenance and a work effort to perform the maintenance.
Wouldn't it be better if there was a one-to-many relationship?
Let's say I have a com
On Jun 4, 2008, at 11:51 AM, Adrian Crum wrote:
It appears to me that there is a one-to-one relationship between a
fixed asset maintenance and a work effort to perform the
maintenance. Wouldn't it be better if there was a one-to-many
relationship?
Let's say I have a company truck fixed a
It appears to me that there is a one-to-one relationship between a fixed
asset maintenance and a work effort to perform the maintenance. Wouldn't
it be better if there was a one-to-many relationship?
Let's say I have a company truck fixed asset. I set up two maintenances
for it: oil change eve
