In Cross Tab view, when are adjacent rows merged?

In Cross Tab view, when are adjacent rows merged?

• A. When the last column values are identical
• B. When two adjacent rows have different values in the second column
• C. When the first two columns have the same value in adjacent rows
• D. When there is a null in the first column

Answer: (C)

The main idea is that merging of adjacent rows in a Cross Tab view happens when the row identifiers repeat across consecutive rows. Specifically, if the values in the leftmost two columns (the first two row keys) are the same in adjacent rows, those rows are merged into a single block to show that they belong to the same group. For example, if the first column shows Region and the second column shows Category, and two consecutive rows both have Region = North and Category = Electronics, those rows will be merged. This makes the display cleaner by avoiding repeated labels for identical row keys. If the last column values are identical or if two adjacent rows differ in the second column, there’s no merging across those rows. A null in the first column would also not trigger merging.

The main idea is that merging of adjacent rows in a Cross Tab view happens when the row identifiers repeat across consecutive rows. Specifically, if the values in the leftmost two columns (the first two row keys) are the same in adjacent rows, those rows are merged into a single block to show that they belong to the same group.

For example, if the first column shows Region and the second column shows Category, and two consecutive rows both have Region = North and Category = Electronics, those rows will be merged. This makes the display cleaner by avoiding repeated labels for identical row keys.

If the last column values are identical or if two adjacent rows differ in the second column, there’s no merging across those rows. A null in the first column would also not trigger merging.