Match rules are simply the rules applied to a given control to distinguish it from other controls around it. Think of them like the instructions a person might give a stranger to have them locate their vehicle in a parking garage. If those instructions are too generic (i.e. I drive a blue car), then they are unlikely to match the correct vehicle. Controls are identified by their hierarchy as well, so in order to match a child of a control, you must first match the parent. In the parking garage example, if you gave the person your license plate number, they would easily locate your car. If you gave them the incorrect floor of the garage, they would never locate it.

In your example, I suspect that you will match the same table on subsequent pages. The concept is pretty simple though. You'll want to store the data from each "table" in a central location. The easiest place to store it is using the lookupTable component. On each page, you'll add the data from the "table" you have interrogated into the lookup table. You'll then click the next page link (or however you navigate to a new page) and acquire the data from that page until you can no longer navigate to a new page.