That is correct.

No. For example, we can use reports with a property processing-only = true and with a Customer table as the main data item.

Recursion is possible. For example, Item Cost Adjustment is done using recursion.

The keyword "continue" is not available for loops.

1.

The most important thing is Next(2) < 1. We know we have 7 customers in total. Method Next(2) means we want to do steps of the size of 2 records, which means we get the customer at positions 1, 3, 5, and 7. The counter is incremented 4 times -> the return value is determined by module counter by 4 -> 4 mod 4 equal 0 -> the return value is 1.

2

Only the first loop is executed as the condition in the middle (Counter = 2) is valid. The first loop has the size of step = 3 which means, records 1 and 4, and 5 (as it is the last one) should be read. However, the condition has another requirement -> Next(...) must return a value equal to or greater than 2. The return value is the number of records read in the last step. In our case, for the last step, this number of records is equal only to 1 (step between the 4th and 5th record). So the Counter is incremented only twice.

If we can use both ways, we should always prefer filters. Filters are much more efficient than looping through records.

Recursion is possible. For example, Item Cost Adjustment is done using recursion.

5.

We do not need to know the number of elements on input. The first statement adds as many elements as missing to 5 (or none, if the input contains more elements) and the second statement deletes all elements with index 6 and higher. All indexes in AL Language start at 1.

At last, the loop just increments the counter for each run of the loop (5 times).

It is used in most cases. However, we can loop through records using other repetitive statements as well as using special object types such as processing only reports.