Correct. And that is what happens with the BPM. It updates the JobHead.Date01 and JobHead.Date02.
Here is the ABL code using the Labor.Update.Pre-Processing method:
FOR EACH ttLaborDtl where ttlabordtl.RowMod="U" NO-LOCK:
FIND FIRST JobHead WHERE JobHead.Company = ttLaborDtl.Company AND JobHead.JobNum = ttLaborDtl.JobNum NO-ERROR.
IF AVAILABLE JobHead THEN DO:
Assign JobHead.Date01 = ttLaborDtl.ClockInDate . /*Last Labor*/
IF Jobhead.Date02 = ? then
Assign JobHead.Date02 = ttlabordtl.ClockInDate . /*First Labor*/
END.
END.
Basically spends no time at all.
Charlie Smith
ESSNER Manufacturing, L.P.
6651 Will Rogers Blvd.
Fort Worth, TX 76140
csmith@...<mailto:csmith@...>
ph: (817) 529-6165
fx: (817) 568-2625
[LOGO_Essner_Manufacturing]
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Thursday, March 26, 2015 2:47 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Re: Pulling Job Released Date into a query.
Are you able to make assumptions about the first and last labor that you can use to filter? For me to save the last labor date to the job header, I'd have to update a field with the current date every time more labor was added.
[Non-text portions of this message have been removed]
Here is the ABL code using the Labor.Update.Pre-Processing method:
FOR EACH ttLaborDtl where ttlabordtl.RowMod="U" NO-LOCK:
FIND FIRST JobHead WHERE JobHead.Company = ttLaborDtl.Company AND JobHead.JobNum = ttLaborDtl.JobNum NO-ERROR.
IF AVAILABLE JobHead THEN DO:
Assign JobHead.Date01 = ttLaborDtl.ClockInDate . /*Last Labor*/
IF Jobhead.Date02 = ? then
Assign JobHead.Date02 = ttlabordtl.ClockInDate . /*First Labor*/
END.
END.
Basically spends no time at all.
Charlie Smith
ESSNER Manufacturing, L.P.
6651 Will Rogers Blvd.
Fort Worth, TX 76140
csmith@...<mailto:csmith@...>
ph: (817) 529-6165
fx: (817) 568-2625
[LOGO_Essner_Manufacturing]
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Thursday, March 26, 2015 2:47 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Re: Pulling Job Released Date into a query.
Are you able to make assumptions about the first and last labor that you can use to filter? For me to save the last labor date to the job header, I'd have to update a field with the current date every time more labor was added.
[Non-text portions of this message have been removed]