I'm getting the following error message when trying to use one as a by. I'm not sure how to fix this.

0 ERROR AT OR NEAR LINE 107 IN PROCEDURE ADHOCRQ FOCEXEC *
(FOC030) ALL VERB OBJECTS MUST BE IN THE SAME PATH AS THEIR SORT FIELDS

Any and all help is greatly apprciated.

Ana

This message has been edited. Last edited by: Kerry,

Do you have a join with this Report? You can try changing it to a unique join...or Take all the fields you need an put them in a hold file...then you can sort the hold file anyway you choose for the report request.

Yes I do have a join. I do a hold from this one but if I need to I will add an extra hold file.

JOIN
CL_ACTS_COMM_W.CL_ACTS_COMM_W.CLM_NO IN CL_ACTS_COMM_W TO MULTIPLE
CL_AUTO_LINE_W.CL_AUTO_LINE_W.CLM_NO IN CL_AUTO_LINE_W AS J3
END
JOIN
CL_ACTS_COMM_W.CL_ACTS_COMM_W.CLM_NO IN CL_ACTS_COMM_W TO MULTIPLE
CL_CLMNT_ASSGNMNT_W.CL_CLMNT_ASSGNMNT_W.CLM_NO IN CL_CLMNT_ASSGNMNT_W AS J4
END
JOIN
CL_ACTS_COMM_W.CL_ACTS_COMM_W.CLM_NO IN CL_ACTS_COMM_W TO MULTIPLE
CL_CLMNT_PROP_DMG_W.CL_CLMNT_PROP_DMG_W.CLM_NO IN CL_CLMNT_PROP_DMG_W AS J5
END
JOIN
CL_ACTS_COMM_W.CL_ACTS_COMM_W.CLM_NO IN CL_ACTS_COMM_W TO MULTIPLE
CL_AUTO_INFO_W.CL_AUTO_INFO_W.CLM_NO IN CL_AUTO_INFO_W AS J6
END

Ana,

Prarie is correct. The standard way to avoid this message is to either make the offending join unique (remove the ALL) or to restructure the query.

As for the hold file, creating another one is no biggie unless they are horribly huge. They just go into edatemp and are deleted after request is complete. Just print your BY fields instead of sorting by them.

Since we don't have your code or the masters, it is difficult to say if you could restructure your report to avoid the message. My technique is to print all the masters and the focexec. Then using different colored markers, I highlight each of the masters in a unique color and then color the fields in the report with the matching color. You can then easily see where in your join structure the fields are coming from. Sometimes this little exercise makes a solution easier to discern.

You have what I call a horizontal join. If you can do what I call a vertical join, cl_acct_comm_w to cl_auto_line_w to cl_clmnt_assigmnt_w to cl_clmnt_prop_dmg_w to cl_auto_info_w or something similar, a hold file is you option with only 'by' from the cl_accts_comm_w as Ginny Says. Depending on your selection the file size can vary. Also with the join structure you have you also need to watch for the infamous 'testing in independent sets of data' issue.

If it gives you the same result you could also try BY TOTAL on your field. At the time the BY TOTAL is processed all verb objects are now in the internal matrix.

So are we saying that WF is unable to sort a result set containing a parent-child relationship by a field in the child table? I have join that is like:

 join flda in tbla to multiple fldb in tblb as j0 

I can make it join unique but that doesn't give me the right result.

Not quite Mac. What they're saying would be like joining file a to file b and file a to file c, then printing a field from each file sorted by a field from c. Field B cannot be sorted by field C as they are not all in the same path.

Now if you joined file a to b and file b to c, then all fields would be in the same path. Clear as mud?

Esdiest way to see this is to use CHECK FILE FILENAME PICTURE which shows the files in the path in visual form (more or less) so you can physically see the path.

Here's an example from CAR and you can see the relationships between segment (or files).

1SECTION 01
 STRUCTURE OF FOCUS    FILE CAR      ON 08/05/08 AT 14.50.05
 ORIGIN
 01      S1
 **************
 *COUNTRY     **I
 *            **
 *            **
 *            **
 *            **
 ***************
 **************
 I
 I
 I
 I COMP
 02    I S1
 **************
 *CAR         **
 *            **
 *            **
 *            **
 *            **
 ***************
 **************
 I
 +-----------------+-----------------+
 I                 I                 I
 I CARREC          I WARANT          I EQUIP
 03    I S1        06    I S1        07    I S1
 **************    **************    **************
 *MODEL       **   *WARRANTY    **   *STANDARD    **
 *            **   *            **   *            **
 *            **   *            **   *            **
 *            **   *            **   *            **
 *            **   *            **   *            **
 ***************   ***************   ***************
 **************    **************    **************
 I
 I
 I
 I BODY
 04    I S1
 **************
 *BODYTYPE    **
 *SEATS       **
 *DEALER_COST **
 *RETAIL_COST **
 *            **
 ***************
 **************
 I
 I
 I
 I SPECS
 05    I U
 **************
 *LENGTH      *
 *WIDTH       *
 *HEIGHT      *
 *WEIGHT      *
 *            *
 **************



  

I searched my issue and found your reply. This fixed my problem. Thanks for the info.

quote:

Originally posted by MacLonghorn:
So are we saying that WF is unable to sort a result set containing a parent-child relationship by a field in the child table? I have join that is like:

 join flda in tbla to multiple fldb in tblb as j0 

I can make it join unique but that doesn't give me the right result.