Its not a job such as a sql job, or anything like that, its a repair job on
a car so time isn't a factor only the number of days.
so if the user body guy enters in a start date of 7/11/2008 and enters in
the number of hours its going to take to do each task, prep, paint, etc.
such as a total of 8 hours, then they should see an end date of 7/12/2008
and so on.
Mark Rae said:
[top-posting corrected]
I have an application that allows the user to pick a start date, then
the enter in a number of hours to do a job, then a stop date fills out
a textbox. Is there a way to find out the stop date?
Yes.
If they pick 7/11/08 and enter in 10 hours for a job, how can I figure
out the actual date the job should end?
Depends what time the job starts. Does it start the moment the user
presses the button, or does it start at 00:00?
There is no particular time for the job to start. The user is only
picking the day which it will start and how many hours it will take to do
the job.
Er, so how can you possibly know when the job ends if you don't know when
it starts...?
Is this for a real application? Your example seems to go against what
you are saying. A job that takes lets say 10 hours, if there is prep
painting etc., the drying of the paint must occur prior to other steps
so the number of hours is not indicative of the time to do the job. And
what happens when an 'emergency' job comes in and the person/people
required to do the job are busy with other work.
Most jobs like this are charged by worktime not by the time the job will
be finished.
LS