[stackoverflow] [progress Openedge Abl] Progress Abl: Break By With Multiple Joins In An...

  • Thread starter Thread starter Corentin
  • Start date Start date
Status
Not open for further replies.
C

Corentin

Guest
I'm pretty new to ABL (and I'm French so please excuse my English) so I need your help. I'd like to know how to use a BREAK BY in an OPEN QUERY.

Here's what I do:

define query Q-REQ for
ENT_RCP_FRN,
LIG_RCP_FRN,
CONSO_UNV_MDIM,
LIG_DOC_TRS,
ENT_DOC_TRS scrolling.

open query Q-REQ for
each ENT_RCP_FRN no-lock
where ENT_RCP_FRN.STO-c-CodeDes = "DRET",
each LIG_RCP_FRN no-lock break by LIG_RCP_FRN.SKU-c-cod
where LIG_RCP_FRN.SOU-c-Cod = ENT_RCP_FRN.SOU-c-Cod
and LIG_RCP_FRN.ERF-c-NumRcpFrn = ENT_RCP_FRN.ERF-c-NumRcpFrn,
each CONSO_UNV_MDIM no-lock
where CONSO_UNV_MDIM.UMA-c-Code = "8B6A9/0001354"
and CUMD-c-LstCleCumConso = LIG_RCP_FRN.SKU-c-cod,
each LIG_DOC_TRS no-lock LEFT OUTER-JOIN
where LIG_DOC_TRS.SKU-c-Cod = LIG_RCP_FRN.SKU-c-Cod,
each ENT_DOC_TRS no-lock left outer-join
where ENT_DOC_TRS.SOU-c-Cod = LIG_DOC_TRS.SOU-c-Cod
and ENT_DOC_TRS.EDT-c-NumDocTrs = LIG_DOC_TRS.EDT-c-NumDocTrs
and ENT_DOC_TRS.TR-c-CodeCatDoc = "BT"
and ENT_DOC_TRS.STO-c-CodeOri = "DRET"
and ENT_DOC_TRS.STO-c-CodeDes = "DWHO".


repeat :

get next Q-REQ.
if not available ENT_RCP_FRN then leave.


end.


I get an error at the following statement:

each LIG_RCP_FRN no-lock break by LIG_RCP_FRN.SKU-c-cod
where LIG_RCP_FRN.SOU-c-Cod = ENT_RCP_FRN.SOU-c-Cod
and LIG_RCP_FRN.ERF-c-NumRcpFrn = ENT_RCP_FRN.ERF-c-NumRcpFrn,


Unable to understand after: "LIG_RCP_FRN.SKU-c-cod" (my error is in French, but it is error 247):

247** L'expression après : "LIG_RCP_FRN.SKU-c-cod" est incompréhensible. (247)

What I'd like to do is to be able to sum a column from the table LIG_RCP_FRN, breaking when the SKU-c-Cod changes.

I tried to delete every statement after this error, but It didn't work neither.

Please ask if you need more information. Openedge progress 10.2A

Thank you for your help, Corentin

PS: impossible to say "Hi" in a post??

Continue reading...
 
Status
Not open for further replies.
Back
Top